Data subject access request processing systems and related methods

ABSTRACT

In particular embodiments, computer-implemented data processing, systems, and method configured to: receive a request to initiate a transaction between an entity and a data subject, generate (i) a consent receipt for the transaction comprising at least a unique subject identifier and a unique consent receipt key and (ii) a unique cookie to identify the data subject&#39;s transaction initiated by the data subject, store the consent receipt for the transaction and the unique cookie, receive a data subject access request from the data subject, verify an identity of the data subject based at least in part on the unique cookie process the request, process the request by identifying one or more pieces of personal data associated with the data subject, and taking one or more actions based at least in part on the data subject access request.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/135,445, filed Dec. 28, 2020, which is a continuation of U.S. patent application Ser. No. 16/983,536, filed Aug. 3, 2020, now U.S. Pat. No. 10,878,127, issued Dec. 29, 2020, which is a continuation-in-part of U.S. patent application Ser. No. 16/881,832, filed May 22, 2020, which claims priority from U.S. Provisional Patent Application Ser. No. 62/852,832, filed May 24, 2019, and is also a continuation-in-part of U.S. patent application Ser. No. 16/834,812, filed Mar. 30, 2020, now U.S. Pat. No. 10,929,559, issued Feb. 23, 2021, which is a continuation of U.S. patent application Ser. No. 16/563,741, filed Sep. 6, 2019, now U.S. Pat. No. 10,607,028, issued Mar. 31, 2020, which claims priority from U.S. Provisional Patent Application Ser. No. 62/728,435, filed Sep. 7, 2018, and is also a continuation-in-part of U.S. patent application Ser. No. 16/410,566, filed May 13, 2019, now U.S. Pat. No. 10,452,866, issued Oct. 22, 2019, which is a continuation-in-part of U.S. patent application Ser. No. 16/055,083, filed Aug. 4, 2018, now U.S. Pat. No. 10,289,870, issued May 14, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/547,530, filed Aug. 18, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, now U.S. Pat. No. 10,181,051, issued Jan. 15, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/537,839 filed Jul. 27, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/853,674, filed Dec. 22, 2017, now U.S. Pat. No. 10,019,597, issued Jul. 10, 2018, which claims priority from U.S. Provisional Patent Application Ser. No. 62/541,613, filed Aug. 4, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/619,455, filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966, issued Dec. 26, 2017, which is a continuation-in-part of U.S. patent application Ser. No. 15/254,901, filed Sep. 1, 2016, now U.S. Pat. No. 9,729,583, issued Aug. 8, 2017, which claims priority from: (1) U.S. Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016; (2) U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016; and (3) U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun. 10, 2016. U.S. patent application Ser. No. 16/881,832 is also a continuation-in-part of U.S. patent application Ser. No. 16/552,765, filed Aug. 27, 2019, now U.S. Pat. No. 10,678,945, issued Jun. 9, 2020, which is a continuation-in-part of U.S. patent application Ser. No. 16/277,568, filed Feb. 15, 2019, now U.S. Pat. No. 10,440,062, issued Oct. 8, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/631,684, filed Feb. 17, 2018 and U.S. Provisional Patent Application Ser. No. 62/631,703, filed Feb. 17, 2018, and is also a continuation-in-part of U.S. patent application Ser. No. 16/159,634, filed Oct. 13, 2018, now U.S. Pat. No. 10,282,692, issued May 7, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/572,096, filed Oct. 13, 2017 and U.S. Provisional Patent Application Ser. No. 62/728,435, filed Sep. 7, 2018, and is also a continuation-in-part of U.S. patent application Ser. No. 16/055,083, filed Aug. 4, 2018, now U.S. Pat. No. 10,289,870, issued May 14, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/547,530, filed Aug. 18, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, now U.S. Pat. No. 10,181,051, issued Jan. 15, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/537,839, filed Jul. 27, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/853,674, filed Dec. 22, 2017, now U.S. Pat. No. 10,019,597, issued Jul. 10, 2018, which claims priority from U.S. Provisional Patent Application Ser. No. 62/541,613, filed Aug. 4, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/619,455, filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966, issued Dec. 26, 2017, which is a continuation-in-part of U.S. patent application Ser. No. 15/254,901, filed Sep. 1, 2016, now U.S. Pat. No. 9,729,583, issued Aug. 8, 2017, which claims priority from: (1) U.S. Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016; (2) U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016; and (3) U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun. 10, 2016. The disclosures of all of the above patent applications are hereby incorporated herein by reference in their entirety.

BACKGROUND

Over the past years, privacy and security policies, and related operations have become increasingly important. Breaches in security, leading to the unauthorized access of personal data (which may include sensitive personal data) have become more frequent among companies and other organizations of all sizes. Such personal data may include, but is not limited to, personally identifiable information (PII), which may be information that directly (or indirectly) identifies an individual or entity. Examples of PII include names, addresses, dates of birth, social security numbers, and biometric identifiers such as a person's fingerprints or picture. Other personal data may include, for example, customers' Internet browsing habits, purchase history, and even their preferences (e.g., likes and dislikes, as provided or obtained through social media).

Many organizations that obtain, use, and transfer personal data, including sensitive personal data, have begun to address these privacy and security issues. To manage personal data, many companies have attempted to implement operational policies and processes that comply with legal and organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example, a right to obtain confirmation of whether a particular organization is processing their personal data, a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected), and other such rights. Some regulations require organizations to comply with requests for such information (e.g., Data Subject Access Requests) within relatively short periods of time (e.g., 30 days).

Existing systems for complying with such requests can be inadequate for producing and providing the required information within the required timelines. This is especially the case for large corporations, which may store data on several different platforms in differing locations. Accordingly, there is a need for improved systems and methods for complying with data subject access requests.

SUMMARY

Various embodiments of a data subject access request fulfillment system and computer-implemented data processing method for responding to one or more data subject access requests are described in the listing of concepts below. Although various concepts are escribed in combination with specific other concepts, it should be understood in light of this disclosure that any concept described in this listing or anywhere else in this disclosure may, in particular embodiments, appear in any suitable combination, may omit certain features, and/or may include any suitable additional features than those described specifically in the context of a particular concept.

1. A computer-implemented data processing method for responding to a data subject access request, in particular embodiments, comprises:

receiving, by one or more processors, a data subject access request from a data subject comprising one or more request parameters;

determining, by one or more processors, that the data subject is associated with a particular geographic location;

verifying, by one or more processors, that the data subject is associated with the particular geographic location by:

-   -   prompting the data subject to provide one or more additional         pieces of information in order to verify that the data subject         is associated with the particular geographic location;     -   receiving the one or more additional pieces of information; and     -   confirming that the data subject is associated with a particular         geographic location based at least in part on the one or more         additional pieces of information;

in response to verifying that the data subject is associated with the particular geographic location, processing, by one or more processors, the request by identifying one or more pieces of personal data associated with the data subject, the one or more pieces of personal data being stored in one or more data repositories associated with a particular organization; and

taking, by one or more processors, one or more actions based at least in part on the data subject access request, the one or more actions including one or more actions related to the one or more pieces of personal data.

2. The computer-implemented data processing method of concept 1, wherein prompting the data subject to provide one or more additional pieces of information in order to verify that the data subject is associated with the particular geographic location further comprises:

generating a secure link between one or more processors associated with the data subject access request and a computing device associated with the data subject to prevent outside access to the one or more additional pieces of information provided by the data subject;

receiving, via the secure link, the one or more additional pieces of information provided by the data subject; and

digitally storing the one or more additional pieces of information provided by the data subject.

3. The computer-implemented data processing method of concept 1, wherein determining that the data subject is associated with a particular geographic location comprises determining that the data subject is a resident of the particular geographic location. 4. The computer-implemented data processing method of concept 1, wherein verifying that the data subject is associated with the particular geographic location further comprises:

accessing, by one or more processors, one or more third-party data aggregation systems; and

comparing, by one or more processors, the one or more additional pieces of information received from the data subject to corresponding data information accessed via one or more third-party data aggregation systems in order to verify that the data subject is associated with the particular geographic location.

5. The computer-implemented data processing method of concept 4, wherein the one or more additional pieces of information received from the data subject identifies an address of residence of the data subject and the method further comprises:

accessing, via the one or more third-party data aggregation systems, one or more property identification databases associated with the particular geographic location;

determining a property identification address of residence of the data subject based at least in part on accessing the one or more property identification databases;

comparing, by one or more processors, the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject; and

verifying, by one or more processors, that the data subject is associated with the particular geographic location based at least in part on the comparing of the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject.

6. The computer-implemented data processing method of concept 4, wherein the one or more additional pieces of information received from the data subject identifies one or more financial records of the data subject and the method further comprises:

determining a geographic location associated with one or more financial transactions based at least in part on the one or more financial records provided by the data subject; and

accessing, via the one or more third-party data aggregation systems, one or more financial record databases;

confirming, by one or more processors, the geographic location associated with the one or more financial transactions is the determined particular geographic location associated with the data subject; and

verifying, by one or more processors, that the data subject is associated with the particular geographic location based at least in part on the confirming that the geographic location associated with the one or more financial transactions is the determined particular geographic location associated with the data subject.

7. The computer-implemented data processing method of concept 1, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

8. The computer-implemented data processing method of concept 1, wherein the one or more additional pieces of information is one or more images provided by the data subject via a computing device associated with the data subject. 9. A computer-implemented data processing method for responding to a data subject access request, in any embodiment described herein, may comprise:

receiving, a data subject access request from a data subject comprising one or more request parameters, wherein the data subject access request includes a particular geographic location identified by the data subject to be a residence geographic location of the data subject;

verifying, by one or more processors, that the data subject is associated with the particular geographic location by:

-   -   accessing one or more third-party data aggregation systems; and     -   confirming the particular geographic location identified by the         data subject to be the residence geographic location of the data         subject based at least in part on accessing the one or more         third-party data aggregation systems;

in response to verifying that the data subject is associated with the particular geographic location, processing, by one or more processors, the request by identifying one or more pieces of personal data associated with the data subject, the one or more pieces of personal data being stored in one or more data repositories associated with a particular organization; and

taking, by one or more processors, one or more actions based at least in part on the data subject access request, the one or more actions including one or more actions related to the one or more pieces of personal data.

10. The computer-implemented data processing method of concept 9, wherein determining that the data subject is associated with a particular geographic location comprises determining that the data subject is a resident of the particular geographic location. 11. The computer-implemented data processing method of concept 9, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

12. The computer-implemented data processing method of concept 9, further comprising:

prompting, by one or more processors, the data subject to provide one or more additional pieces of information in order to verify that the data subject is associated with the particular geographic location;

receiving, by one or more processors, the one or more additional pieces of information; and

comparing, by one or more processors, the one or more additional pieces of information received from the data subject to corresponding data information accessed via one or more third-party data aggregation systems in order to verify that the data subject is associated with the particular geographic location.

13. A data subject access request processing system in various embodiments, comprises:

one or more data subject access request management servers;

a plurality of local storage nodes, each of the plurality of local storage nodes being physically located in a distinct geographic location;

one or more processers; and

memory, wherein the one or more processers are configured for:

-   -   receiving, a data subject access request from a data subject         comprising one or more request parameters;     -   determining that the data subject is associated with a         particular geographic location;     -   verifying that the data subject is associated with the         particular geographic location by:         -   prompting the data subject to provide one or more additional             pieces of information in order to verify that the data             subject is associated with the particular geographic             location;         -   receiving the one or more additional pieces of information;             and         -   confirming that the data subject is associated with a             particular geographic location based at least in part on the             one or more additional pieces of information;     -   in response to verifying that the data subject is associated         with the particular geographic location, processing the request         by identifying one or more pieces of personal data associated         with the data subject, the one or more pieces of personal data         being stored in one or more data repositories associated with a         particular organization; and     -   taking one or more actions based at least in part on the data         subject access request, the one or more actions including one or         more actions related to the one or more pieces of personal data.         14. The data subject access request processing system of concept         13, wherein prompting the data subject to provide one or more         additional pieces of information in order to verify that the         data subject is associated with the particular geographic         location further comprises:

generating a secure link between one or more processors associated with the data subject access request and a computing device associated with the data subject to prevent outside access to the one or more additional pieces of information provided by the data subject;

receiving, via the secure link, the one or more additional pieces of information provided by the data subject; and

digitally storing the one or more additional pieces of information provided by the data subject.

15. The data subject access request processing system of concept 13, wherein determining that the data subject is associated with a particular geographic location comprises determining that the data subject is a resident of the particular geographic location. 16. The data subject access request processing system of concept 13, wherein verifying that the data subject is associated with the particular geographic location further comprises:

accessing one or more third-party data aggregation systems; and

comparing the one or more additional pieces of information received from the data subject to corresponding data information accessed via one or more third-party data aggregation systems in order to verify that the data subject is associated with the particular geographic location.

17. The data subject access request processing system of concept 16, wherein the one or more additional pieces of information received from the data subject identifies an address of residence of the data subject and the method further comprises:

accessing, via the one or more third-party data aggregation systems, one or more property identification databases associated with the particular geographic location;

determining a property identification address of residence of the data subject based at least in part on accessing the one or more property identification databases;

comparing the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject; and

verifying that the data subject is associated with the particular geographic location based at least in part on the comparing of the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject.

18. The data subject access request processing system of concept 16, wherein the one or more additional pieces of information received from the data subject identifies one or more financial records of the data subject and the method further comprises:

determining a geographic location associated with one or more financial transactions based at least in part on the one or more financial records provided by the data subject; and

accessing, via the one or more third-party data aggregation systems, one or more financial record databases;

confirming the geographic location associated with the one or more financial transactions is the determined particular geographic location associated with the data subject; and

verifying that the data subject is associated with the particular geographic location based at least in part on the confirming that the geographic location associated with the one or more financial transactions is the determined particular geographic location associated with the data subject.

19. The data subject access request processing system of concept 13, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

20. The data subject access request processing system of concept 13, wherein the one or more additional pieces of information is one or more images provided by the data subject via a computing device associated with the data subject.

Various other embodiments of a data subject access request fulfillment system and computer-implemented data processing method for responding to one or more data subject access requests are described in the listing of concepts below.

1. A computer-implemented data processing method for verifying a data subject of a data subject access request, according to particular embodiments, comprises:

receiving a request to initiate a transaction between an entity and a data subject, the transaction being initiated by the data subject via a user interface and involving collection or processing of personal data associated with the data subject by the entity as part of a processing activity undertaken by the entity that the data subject is consenting to as part of the transaction;

in response to receiving the request to initiate the transaction, generating:

-   -   a consent receipt for the transaction comprising at least a         unique subject identifier and a unique consent receipt key; and     -   a unique cookie to identify the data subject's transaction         initiated by the data subject;

storing, by one or more processors, the consent receipt for the transaction and the unique cookie;

receiving, by one or more processors, a data subject access request from the data subject comprising one or more request parameters;

verifying, by one or more processors, an identity of the data subject based at least in part on the unique cookie;

in response to verifying the identity of the data subject, processing, by one or more processors, the request by identifying one or more pieces of personal data associated with the data subject, the one or more pieces of personal data being stored in one or more data repositories associated with the entity; and

taking, by one or more processors, one or more actions based at least in part on the data subject access request, the one or more actions including one or more actions related to the one or more pieces of personal data.

2. The computer-implemented data processing method of concept 1, further comprising:

in response to generating (i) the consent receipt and (ii) the unique cookie to identify the data subject's transaction, providing, by one or more processors, (i) the consent receipt and (ii) the unique cookie to identify the data subject's transaction to the data subject.

3. The computer-implemented data processing method of concept 2, wherein the unique cookie provided to the data subject is stored within a web browser associated with an electronic device of the data subject. 4. The computer-implemented data processing method of concept 3, wherein verifying the identity of the data subject based at least in part on the unique cookie further comprises:

accessing, by one or more processors, one or more cookies stored within the web browser associated with the electronic device of the data subject;

comparing, by one or more processors, (i) the one or more cookies stored within the web browser associated with the electronic device of the data subject to (ii) the unique cookie;

determining, by one or more processors, that the one or more cookies stored within the web browser associated with the electronic device of the data subject includes the unique cookie; and

in response, verifying, by one or more processors, the identity of the data subject.

5. The computer-implemented data processing method of concept 3, wherein verifying the identity of the data subject based at least in part on the unique cookie further comprises:

accessing, by one or more processors, one or more cookies stored within the web browser associated with the electronic device of the data subject;

comparing, by one or more processors, (i) the one or more cookies stored within the web browser associated with the electronic device of the data subject to (ii) the unique cookie;

determining, by one or more processors, that the one or more cookies stored within the web browser associated with the electronic device of the data subject does not include the unique cookie;

in response, generating, by one or more processors, a notification to provide to the data subject indicating that the identity of the data subject cannot be verified; and

providing, by one or more processors, the notification to the electronic device associated with the data subject.

6. The computer-implemented data processing method of concept 1, wherein generating the consent receipt further comprises:

in response to receiving the request, the method further comprises:

-   -   identifying a transaction identifier associated with the         transaction;     -   generating the unique consent receipt key for the transaction;         and     -   determining the unique subject identifier for the data subject;

electronically storing the unique subject identifier, the unique consent receipt key, and the transaction identifier in computer memory;

electronically associating the unique subject identifier, the unique consent receipt key, and the transaction identifier;

generating the consent record for the transaction; and

electronically storing the consent record.

7. The computer-implemented data processing method of concept 6, further comprising:

electronically transmitting the consent record to the data subject.

8. The computer-implemented data processing method of concept 1, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

9. A computer-implemented data processing method for verifying a data subject of a data subject access request, in various embodiments, comprises:

receiving a request to initiate a transaction between an entity and a data subject, the transaction being initiated by the data subject via a user interface and involving collection or processing of personal data associated with the data subject by the entity as part of a processing activity undertaken by the entity that the data subject is consenting to as part of the transaction;

in response to receiving the request to initiate the transaction, generating a unique cookie to identify the data subject's transaction initiated by the data subject;

storing, by one or more processors, the unique cookie;

receiving, by one or more processors, a data subject access request from the data subject comprising one or more request parameters;

verifying, by one or more processors, an identity of the data subject based at least in part on the unique cookie by:

-   -   accessing, by one or more processors, one or more cookies stored         within a web browser associated with the electronic device of         the data subject,     -   comparing, by one or more processors, (i) the one or more         cookies stored within the web browser associated with the         electronic device of the data subject to (ii) the unique cookie,         and     -   determining, by one or more processors, that the one or more         cookies stored within the web browser associated with the         electronic device of the data subject includes the unique         cookie;

in response to verifying the identity of the data subject, processing, by one or more processors, the request by identifying one or more pieces of personal data associated with the data subject, the one or more pieces of personal data being stored in one or more data repositories associated with the entity; and

taking, by one or more processors, one or more actions based at least in part on the data subject access request, the one or more actions including one or more actions related to the one or more pieces of personal data.

10. The computer-implemented data processing method of concept 9, further comprising:

providing the unique cookie to the data subject, wherein the unique cookie is stored within a web browser associated with an electronic device of the data subject.

11. The computer-implemented data processing method of concept 9, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

12. The computer-implemented data processing method of concept 9, further comprising:

generating a consent receipt for the transaction comprising at least a unique subject identifier and a unique consent receipt key; and

storing the consent receipt for the transaction.

13. A data subject access request processing system, in any embodiment described herein, may comprise:

one or more data subject access request management servers;

a plurality of local storage nodes, each of the plurality of local storage nodes being physically located in a distinct geographic location;

one or more processers; and

memory, wherein the one or more processers are configured for:

-   -   receiving a request to initiate a transaction between an entity         and a data subject, the transaction being initiated by the data         subject via a user interface and involving collection or         processing of personal data associated with the data subject by         the entity as part of a processing activity undertaken by the         entity that the data subject is consenting to as part of the         transaction;     -   in response to receiving the request to initiate the         transaction, generating:         -   a consent receipt for the transaction comprising at least a             unique subject identifier and a unique consent receipt key;             and         -   a unique cookie to identify the data subject's transaction             initiated by the data subject;     -   storing the consent receipt for the transaction and the unique         cookie;     -   receiving a data subject access request from the data subject         comprising one or more request parameters;     -   verifying an identity of the data subject based at least in part         on the unique cookie;     -   in response to verifying the identity of the data subject,         processing the request by identifying one or more pieces of         personal data associated with the data subject, the one or more         pieces of personal data being stored in one or more data         repositories associated with the entity; and     -   taking one or more actions based at least in part on the data         subject access request, the one or more actions including one or         more actions related to the one or more pieces of personal data.         14. The data subject access request processing system of concept         13, wherein the one or more processers are further configured         for:

in response to generating (i) the consent receipt and (ii) the unique cookie to identify the data subject's transaction, providing, by one or more processors, (i) the consent receipt and (ii) the unique cookie to identify the data subject's transaction to the data subject.

15. The data subject access request processing system of concept 14, wherein the unique cookie provided to the data subject is stored within a web browser associated with an electronic device of the data subject. 16. The data subject access request processing system of concept 15, wherein verifying the identity of the data subject based at least in part on the unique cookie further comprises:

accessing one or more cookies stored within the web browser associated with the electronic device of the data subject;

comparing (i) the one or more cookies stored within the web browser associated with the electronic device of the data subject to (ii) the unique cookie;

determining that the one or more cookies stored within the web browser associated with the electronic device of the data subject includes the unique cookie; and

in response, verifying the identity of the data subject.

17. The data subject access request processing system of concept 15, wherein verifying the identity of the data subject based at least in part on the unique cookie further comprises:

accessing one or more cookies stored within the web browser associated with the electronic device of the data subject;

comparing (i) the one or more cookies stored within the web browser associated with the electronic device of the data subject to (ii) the unique cookie;

determining that the one or more cookies stored within the web browser associated with the electronic device of the data subject does not include the unique cookie;

in response, generating a notification to provide to the data subject indicating that the identity of the data subject cannot be verified; and

providing the notification to the electronic device associated with the data subject.

18. The data subject access request processing concept of 13, wherein generating the consent receipt further comprises:

in response to receiving the request, the method further comprises:

-   -   identifying a transaction identifier associated with the         transaction;     -   generating the unique consent receipt key for the transaction;         and     -   determining the unique subject identifier for the data subject;

electronically storing the unique subject identifier, the unique consent receipt key, and the transaction identifier in computer memory;

electronically associating the unique subject identifier, the unique consent receipt key, and the transaction identifier;

generating the consent record for the transaction; and

electronically storing the consent record.

19. The data subject access request processing system of concept 18, further comprising: electronically transmitting the consent record to the data subject. 20. The data subject access request processing system of concept 13, wherein one of the one or more request parameters of the data subject access request comprises a type of data subject access request, and wherein the type of data subject access request may include, for example:

a subject's rights request, and

a data subject deletion request.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a data subject access request fulfillment system are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 depicts a data subject request processing and fulfillment system according to particular embodiments.

FIG. 2A is a schematic diagram of a computer (such as the data model generation server 110, or data model population server 120 of FIG. 1) that is suitable for use in various embodiments of the data subject request processing and fulfillment system shown in FIG. 1.

FIG. 2B is a flow chart depicting exemplary steps executed by a Data Subject Access Request Routing Module according to a particular embodiment

FIGS. 3-43 are computer screen shots that demonstrate the operation of various embodiments.

FIGS. 44-49 depict various exemplary screen displays and user interfaces that a user of various embodiments of the system may encounter (FIGS. 47 and 48 collectively show four different views of a Data Subject Request Queue).

FIG. 50 is a flowchart showing an example of processes performed by an Orphaned Data Action Module 5000 according to various embodiments.

FIG. 51 is a flowchart showing an example of processes performed by a Personal Data Deletion and Testing Module 5100 according to various embodiments.

FIG. 52 is a flowchart showing an example of processes performed by a Data Risk Remediation Module 5200 according to various embodiments.

FIG. 53 is a flowchart showing an example of processes performed by a Central Consent Module 5300 according to various embodiments.

FIG. 54 is a flowchart showing an example of processes performed by a Data Transfer Risk Identification Module 5400 according to various embodiments.

FIG. 55 is a flowchart showing an example of steps performed by a Data Model Generation Module according to particular embodiments.

FIGS. 56-62 depict various exemplary visual representations of data models according to particular embodiments.

FIG. 63 is a flowchart showing an example of steps performed by a Data Model Population Module.

FIG. 64 is a flowchart showing an example of steps performed by a Data Population Questionnaire Generation Module.

FIG. 65 is a process flow for populating a data inventory according to a particular embodiment using one or more data mapping techniques.

FIG. 66 is a flowchart showing an example of steps performed by an Intelligent Identity Scanning Module.

FIG. 67 is schematic diagram of network architecture for an intelligent identity scanning system 2700 according to a particular embodiment.

FIG. 68 is a schematic diagram of an asset access methodology utilized by an intelligent identity scanning system 2700 in various embodiments of the system.

FIG. 69 is a flowchart showing an example of a processes performed by a Data Subject Access Request Fulfillment Module 2900 according to various embodiments.

FIG. 70 is a flow chart showing an example of a process performed by a Data Subject Verification Module according to particular embodiments.

FIG. 71 is a flow chart showing an example of a process performed by a Data Subject Cookie Verification Module according to particular embodiments.

DETAILED DESCRIPTION

Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.

Overview

A data model generation and population system, according to particular embodiments, is configured to generate a data model (e.g., one or more data models) that maps one or more relationships between and/or among a plurality of data assets utilized by a corporation or other entity (e.g., individual, organization, etc.) in the context, for example, of one or more business processes. In particular embodiments, each of the plurality of data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, web site, data-center, server, etc.). For example, a first data asset may include any software or device (e.g., server or servers) utilized by a particular entity for such data collection, processing, transfer, storage, etc.

As shown in FIGS. 4 and 5, in various embodiments, the data model may store the following information: (1) the organization that owns and/or uses a particular data asset (a primary data asset, which is shown in the center of the data model in FIG. 4); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset (e.g., or one or more other suitable collection assets from which the personal data that is collected, processed, stored, etc. by the primary data asset is sourced); (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets. As shown in FIGS. 6 and 7, the system may also optionally store information regarding, for example, which business processes and processing activities utilize the data asset.

In particular embodiments, the data model stores this information for each of a plurality of different data assets and may include links between, for example, a portion of the model that provides information for a first particular data asset and a second portion of the model that provides information for a second particular data asset.

In various embodiments, the data model generation and population system may be implemented in the context of any suitable privacy management system that is configured to ensure compliance with one or more legal or industry standards related to the collection and/or storage of private information. In various embodiments, a particular organization, sub-group, or other entity may initiate a privacy campaign or other activity (e.g., processing activity) as part of its business activities. In such embodiments, the privacy campaign may include any undertaking by a particular organization (e.g., such as a project or other activity) that includes the collection, entry, and/or storage (e.g., in memory) of any personal data associated with one or more individuals. In particular embodiments, a privacy campaign may include any project undertaken by an organization that includes the use of personal data, or any other activity that could have an impact on the privacy of one or more individuals.

In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein. In particular embodiments, such personal data may include one or more cookies (e.g., where the individual is directly identifiable or may be identifiable based at least in part on information stored in the one or more cookies).

In particular embodiments, when generating a data model, the system may, for example: (1) identify one or more data assets associated with a particular organization; (2) generate a data inventory for each of the one or more data assets, where the data inventory comprises information such as: (a) one or more processing activities associated with each of the one or more data assets, (b) transfer data associated with each of the one or more data assets (data regarding which data is transferred to/from each of the data assets, and which data assets, or individuals, the data is received from and/or transferred to, (c) personal data associated with each of the one or more data assets (e.g., particular types of data collected, stored, processed, etc. by the one or more data assets), and/or (d) any other suitable information; and (3) populate the data model using one or more suitable techniques.

In particular embodiments, the one or more techniques for populating the data model may include, for example: (1) obtaining information for the data model by using one or more questionnaires associated with a particular privacy campaign, processing activity, etc.; (2) using one or more intelligent identity scanning techniques discussed herein to identify personal data stored by the system and map such data to a suitable data model, data asset within a data model, etc.; (3) obtaining information for the data model from a third-party application (or other application) using one or more application programming interfaces (API); and/or (4) using any other suitable technique.

In particular embodiments, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). In still other embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques described herein.

As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. By generating and populating a data model of one or more data assets that are involved in the collection, storage and processing of such personal data, the system may be configured to create a data model that facilitates a straightforward retrieval of information stored by the organization as desired. For example, in various embodiments, the system may be configured to use a data model in substantially automatically responding to one or more data access requests by an individual (e.g., or other organization). Various embodiments of a system for generating and populating a data model are described more fully below.

Ticket management systems, according to various embodiments, are adapted to receive data subject access requests (DSAR's) from particular data subjects, and to facilitate the timely processing of valid DSAR's by an appropriate respondent. In particular embodiments, the ticket management system receives DSAR's via one or more webforms that each may, for example, respectively be accessed via an appropriate link/button on a respective web page. In other embodiments, the system may receive DSAR's through any other suitable mechanism, such as via a computer software application (e.g., a messaging application such as Slack, Twitter), via a chat bot, via generic API input from another system, or through entry by a representative who may receive the information, for example, via suitable paper forms or over the phone.

The ticket management system may include a webform creation tool that is adapted to allow a user to create customized webforms for receiving DSAR's from various different data subject types and for routing the requests to appropriate individuals for processing. The webform creation tool may, for example, allow the user to specify the language that the form will be displayed in, what particular information is to be requested from the data subject and/or provided by the data subject, who any DSAR's that are received via the webform will be routed to, etc. In particular embodiments, after the user completes their design of the webform, the webform creation tool generates code for the webform that may be cut and then pasted into a particular web page.

The system may be further adapted to facilitate processing of DSAR's that are received via the webforms, or any other suitable mechanism. For example, the ticket management system may be adapted to execute one or more of the following steps for each particular DSAR received via the webforms (or other suitable mechanism) described above: (1) before processing the DSAR, confirm that the DSAR was actually submitted by the particular data subject of the DSAR (or, for example, by an individual authorized to make the DSAR on the data subject's behalf, such as a parent, guardian, power-of-attorney holder, etc.)—any suitable method may be used to confirm the identity of the entity/individual submitting the DSAR—for example, if the system receives the DSAR via a third-party computer system, the system may validate authentication via API secret, or by requiring a copy of one or more particular legal documents (e.g., a particular contract between two particular entities)—the system may validate the identity of an individual by, for example, requiring the individual (e.g., data subject) to provide particular account credentials, by requiring the individual to provide particular out-of-wallet information, through biometric scanning of the individual (e.g., finger or retinal scan), or via any other suitable identity verification technique; (2) if the DSAR was not submitted by the particular data subject, deny the request; (3) if the DSAR was submitted by the particular data subject, advance the processing of the DSAR; (4) route the DSAR to the correct individual(s) or groups internally for handling; (5) facilitate the assignment of the DSAR to one or more other individuals for handling of one or more portions of the DSAR; (6) facilitate the suspension of processing of the data subject's data by the organization; and/or (7) change the policy according to which the data subject's personal data is retained and/or processed by the system. In particular embodiments, the system may perform any one or more of the above steps automatically. The system then generates a receipt for the DSAR request that the user can use as a transactional record of their submitted request.

In particular embodiments, the ticket management system may be adapted to generate a graphical user interface (e.g., a DSAR request-processing dashboard) that is adapted to allow a user (e.g., a privacy officer of an organization that is receiving the DSAR) to monitor the progress of any of the DSAR requests. The GUI interface may display, for each DSAR, for example, an indication of how much time is left (e.g., quantified in days and/or hours) before a legal and/or internal deadline to fulfill the request. The system may also display, for each DSAR, a respective user-selectable indicium that, when selected, may facilitate one or more of the following: (1) verification of the request; (2) assignment of the request to another individual; (3) requesting an extension to fulfill the request; (4) rejection of the request; or (5) suspension of the request.

As noted immediately above, and elsewhere in this application, in particular embodiments, any one or more of the above steps may be executed by the system automatically. As a particular example, the system may be adapted to automatically verify the identity of the DSAR requestor and then automatically fulfill the DSAR request by, for example, obtaining the requested information via a suitable data model and communicating the information to the requestor. As another particular example, the system may be configured to automatically route the DSAR to the correct individual for handling based at least in part on one or more pieces of information provided (e.g., in the webform).

In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

Examples of metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of request; (2) the location from which the request is being made; (3) the country of residency of the data subject and, for example, that county's tolerance for enforcing DSAR violations; (4) current sensitivities to world events; (5) a status of the requestor (e.g., especially loyal customer); or (6) any other suitable metadata.

In particular embodiments, any entity (e.g., organization, company, etc.) that collects, stores, processes, etc. personal data may require one or more of: (1) consent from a data subject from whom the personal data is collected and/or processed; and/or (2) a lawful basis for the collection and/or processing of the personal data. In various embodiments, the entity may be required to, for example, demonstrate that a data subject has freely given specific, informed, and unambiguous indication of the data subject's agreement to the processing of his or her personal data for one or more specific purposes (e.g., in the form of a statement or clear affirmative action). As such, in particular embodiments, an organization may be required to demonstrate a lawful basis for each piece of personal data that the organization has collected, processed, and/or stored. In particular, each piece of personal data that an organization or entity has a lawful basis to collect and process may be tied to a particular processing activity undertaken by the organization or entity.

A particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, because of the number of processing activities that an organization may undertake, and the amount of data collected as part of those processing activities over time, one or more data systems associated with an entity or organization may store or continue to store data that is not associated with any particular processing activity (e.g., any particular current processing activity). Under various legal and industry standards related to the collection and storage of personal data, the organization or entity may not have or may no longer have a legal basis to continue to store the data. As such, organizations and entities may require improved systems and methods to identify such orphaned data, and take corrective action, if necessary (e.g., to ensure that the organization may not be in violation of one or more legal or industry regulations).

In various embodiments, an orphaned personal data identification system may be configured to generate a data model (e.g., one or more data models) that maps one or more relationships between and/or among a plurality of data assets utilized by a corporation or other entity (e.g., individual, organization, etc.) in the context, for example, of one or more business processes or processing activities. In particular embodiments, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). In still other embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques. In still other embodiments, the system is configured to access an existing data model that maps personal data stored by one or more organization systems to particular associated processing activities.

In various embodiments, the system may analyze the data model to identify personal data that has been collected and stored using one or more computer systems operated and/or utilized by a particular organization where the personal data is not currently being used as part of any privacy campaigns, processing activities, etc. undertaken by the particular organization. This data may be described as orphaned data. In some circumstances, the particular organization may be exposed to an increased risk that the data may be accessed by a third party (e.g., cybercrime) or that the particular organization may not be in compliance with one or more legal or industry requirements related to the collection, storage, and/or processing of this orphaned data.

Additionally, in some implementations, in response to the termination of a particular privacy campaign, processing activity, (e.g., manually or automatically), the system may be configured to analyze the data model to determine whether any of the personal data that has been collected and stored by the particular organization is now orphaned data (e.g., whether any personal data collected and stored as part of the now-terminated privacy campaign is being utilized by any other processing activity, has some other legal basis for its continued storage, etc.).

In additional implementations in response to determining that a particular privacy campaign, processing activity, etc. has not been utilized for a period of time (e.g., a day, month, year), the system may be configured to terminate the particular privacy campaign, processing activity, etc. or prompt one or more individuals associated with the particular organization to indicate whether the particular privacy campaign, processing activity, etc. should be terminated or otherwise discontinued.

For example, a particular processing activity may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). As part of the processing activity, the particular company may have collected and stored e-mail addresses for customers that elected to receive (e.g., consented to the receipt of) promotional e-mails. In response to determining that the particular company has not sent out any promotional e-mails for at least a particular amount of time (e.g., for at least a particular number of months), the system may be configured to: (1) automatically terminate the processing activity; (2) identify any of the personal data collected as part of the processing activity that is now orphaned data (e.g., the e-mail addresses); and (3) automatically delete the identified orphaned data. The processing activity may have ended for any suitable reason (e.g., because the promotion that drove the periodic e-mails has ended). As may be understood in light of this disclosure, because the particular organization no longer has a valid basis for continuing to store the e-mail addresses of the customers once the e-mail addresses are no longer being used to send promotional e-mails, the organization may wish to substantially automate the removal of personal data stored in its computer systems that may place the organization in violation of one or more personal data storage rules or regulations.

When the particular privacy campaign, processing activity, etc. is terminated or otherwise discontinued, the system may use the data model to determine if any of the associated personal data that has been collected and stored by the particular organization is now orphaned data.

In various embodiments, the system may be configured to identify orphaned data of a particular organization and automatically delete the data. In some implementations, in response to identifying the orphaned data, the system may present the data to one or more individuals associated with the particular organization (e.g., a privacy officer) and prompt the one or more individuals to indicate why the orphaned data is being stored by the particular organization. The system may then enable the individual to provide one or more valid reasons for the data's continued storage, or enable the one or more individuals to delete the particular orphaned data. In some embodiments, the system may automatically delete the orphaned data if, for example: (1) in response to determining that a reason provided by the individual is not a sufficient basis for the continued storage of the personal data; (2) the individual does not respond to the request to provide one or more valid reasons in a timely manner; (3) etc. In some embodiments, one or more other individuals may review the response provided indicating why the orphaned data is being stored, and in some embodiments, the one or more other individuals can delete the particular orphaned data.

In various embodiments, the system may be configured to review the data collection policy (e.g., how data is acquired, security of data storage, who can access the data, etc.) for the particular organization as well as one or more data retention metrics for the organization. For example, the one or more data retention metrics may include how much personal data is being collected, how long the data is held, how many privacy campaigns or other processes are using the personal data, etc. Additionally, the system may compare the particular organization's data collection policy and data retention metrics to the industry standards (e.g., in a particular field, based on a company size, etc.). In various embodiments, the system may be configured to generate a report that includes the comparison and provide the report to the particular organization (e.g., in electronic format).

In particular embodiments, the system may be configured advise the particular organization to delete data and identify particular data that should be deleted. In some embodiments, the system may automatically delete particular data (e.g., orphaned data). Further, the system may be configured to calculate and provide a risk score for particular data or the organization's data collection policy overall. In particular embodiments, the system may be configured to calculate the risk score based on the combinations of personal data elements in the data inventory of the organization (e.g., where an individual's phone number is stored in one location and their mailing address is stored in another location), and as such the risk may be increased because the additional pieces of personal information can make the stored data more sensitive.

In particular embodiments, any entity (e.g., organization, company, etc.) that collects, stores, processes, etc. personal data may require one or more of: (1) consent from a data subject from whom the personal data is collected and/or processed; and/or (2) a lawful basis for the collection and/or processing of the personal data. In various embodiments, the entity may be required to, for example, demonstrate that a data subject has freely given specific, informed, and unambiguous indication of the data subject's agreement to the processing of his or her personal data for one or more specific purposes (e.g., in the form of a statement or clear affirmative action). As such, in particular embodiments, an organization may be required to demonstrate a lawful basis for each piece of personal data that the organization has collected, processed, and/or stored. In particular, each piece of personal data that an organization or entity has a lawful basis to collect and process may be tied to a particular processing activity undertaken by the organization or entity.

A particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, because of the number of processing activities that an organization may undertake, and the amount of data collected as part of those processing activities over time, one or more data systems associated with an entity or organization may store or continue to store data that is not associated with any particular processing activity (e.g., any particular current processing activity). Under various legal and industry standards related to the collection and storage of personal data, such data may not have or may no longer have a legal basis for the organization or entity to continue to store the data. As such, organizations and entities may require improved systems and methods to maintain an inventory of data assets utilized to process and/or store personal data for which a data subject has provided consent for such storage and/or processing.

In various embodiments, the system is configured to provide a third-party data repository system to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects, as described herein. Additionally, the third-party data repository system is configured to interface with a centralized consent receipt management system.

In particular embodiments, the system may be configured to use one or more website scanning tools to, for example, identify a form (e.g., a webform) and locate a data asset where the input data is transmitted (e.g., Salesforce). Additionally, the system may be configured to add the data asset to the third-party data repository (e.g., and/or data map/data inventory) with a link to the form. In response to a user inputting form data (e.g., name, address, credit card information, etc.) of the form and submitting the form, the system may, based on the link to the form, create a unique subject identifier to submit to the third-party data repository and, along with the form data, to the data asset. Further, the system may use the unique subject identifier of a user to access and update each of the data assets of the particular organization. For example, in response to a user submitting a data subject access request to delete the user's personal data that the particular organization has stored, the system may use the unique subject identifier of the user to access and delete the user's personal data stored in all of the data assets (e.g., Salesforce, Eloqua, Marketo, etc.) utilized by the particular organization.

The system may, for example: (1) generate, for each of a plurality of data subjects, a respective unique subject identifier in response to submission, by each data subject, of a particular form; (2) maintain a database of each respective unique subject identifier; and (3) electronically link each respective unique subject identifier to each of: (A) a form initially submitted by the user; and (B) one or more data assets that utilize data received from the data subject via the form.

In various embodiments, the system may be configured to, for example: (1) identify a form used to collect one or more pieces of personal data, (2) determine a data asset of a plurality of data assets of the organization where input data of the form is transmitted, (3) add the data asset to the third-party data repository with an electronic link to the form, (4) in response to a user submitting the form, create a unique subject identifier to submit to the third-party data repository and, along with the form data provided by the user in the form, to the data asset, (5) submit the unique subject identifier and the form data provided by the user in the form to the third-party data repository and the data asset, and (6) digitally store the unique subject identifier and the form data provided by the user in the form in the third-party data repository and the data asset.

In some embodiments, the system may be further configured to, for example: (1) receive a data subject access request from the user (e.g., a data subject rights' request, a data subject deletion request, etc.), (2) access the third-party data repository to identify the unique subject identifier of the user, (3) determine which data assets of the plurality of data assets of the organization include the unique subject identifier, (4) access personal data of the user stored in each of the data assets of the plurality of data assets of the organization that include the unique subject identifier, and (5) take one or more actions based on the data subject access request (e.g., delete the accessed personal data in response to a data subject deletion request).

Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an entity. In particular, under various privacy and security policies, a data subject may be entitled to a right to erasure of any personal data associated with that data subject that has been at least temporarily stored by the entity (e.g., a right to be forgotten). In various embodiments, under the right to erasure, an entity (e.g., a data controller on behalf of another organization) may be obligated to erase personal data without undue delay under one or more of the following conditions: (1) the personal data is no longer necessary in relation to a purpose for which the data was originally collected or otherwise processed; (2) the data subject has withdrawn consent on which the processing of the personal data is based (e.g., and there is no other legal grounds for such processing); (3) the personal data has been unlawfully processed; (4) the data subject has objected to the processing and there is no overriding legitimate grounds for the processing of the data by the entity; and/or (5) for any other suitable reason or under any other suitable conditions.

In particular embodiments, a personal data deletion system may be configured to: (1) at least partially automatically identify and delete personal data that an entity is required to erase under one or more of the conditions discussed above; and (2) perform one or more data tests after the deletion to confirm that the system has, in fact, deleted any personal data associated with the data subject.

In particular embodiments, in response to a data subject submitting a request to delete their personal data from an entity's systems, the system may, for example: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., deleting a directory entry associated with the data); and/or (3) using any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system may use any suitable data modelling technique to efficiently determine where all of the data subject's personal data is stored.

In various embodiments, the system may be configured to store (e.g., in memory) an indication that the data subject has requested to delete any of their personal data stored by the entity has been processed. Under various legal and industry policies/standards, the entity may have a certain period of time (e.g., a number of days) in order to comply with the one or more requirements related to the deletion or removal of personal data in response to receiving a request from the data subject or in response to identifying one or more of the conditions requiring deletion discussed above. In response to the receiving of an indication that the deletion request for the data subject's personal data has been processed or the certain period of time (described above) has passed, the system may be configured to perform a data test to confirm the deletion of the data subject's personal data.

In particular embodiments, when performing the data test, the system may be configured to provide an interaction request to the entity on behalf of the data subject. In particular embodiments, the interaction request may include, for example, a request for one or more pieces of data associated with the data subject (e.g., account information, etc.). In various embodiments, the interaction request is a request to contact the data subject (e.g., for any suitable reason). The system may, for example, be configured to substantially automatically complete a contact-request form (e.g., a webform made available by the entity) on behalf of the data subject. In various embodiments, when automatically completing the form on behalf of the data subject, the system may be configured to only provide identifying data, but not provide any contact data. In response to submitting the interaction request (e.g., submitting the webform), the system may be configured to determine whether the one or more computers systems have generated and/or transmitted a response to the data subject. The system may be configured to determine whether the one or more computers systems have generated and/or transmitted the response to the data subject by, for example, analyzing one or more computer systems associated with the entity to determine whether the one or more computer systems have generated a communication to the data subject (e.g., automatically) for transmission to an e-mail address or other contact method associated with the data subject, generated an action-item for an individual to contact the data subject at a particular contact number, etc.

In response to determining that the one or more computer systems has generated and/or transmitted the response to the data subject, the system may be configured to determine that the one or more computer systems has not complied with the data subject's request for deletion of their personal data from the one or more computers systems associated with the entity. In response, the system may generate an indication that the one or more computer systems has not complied with the data subject's request for deletion of their personal data from the one or more computers systems have, and store the indication in computer memory.

To perform the data test, for example, the system may be configured to: (1) access (e.g., manually or automatically) a form for the entity (e.g., a web-based “Contact Us” form); (2) input a unique identifier associated with the data subject (e.g., a full name or customer ID number) without providing contact information for the data subject (e.g., mailing address, phone number, email address, etc.); and (3) input a request, within the form, for the entity to contact the data subject to provide information associated with the data subject (e.g., the data subject's account balance with the entity). In response to submitting the form to the entity, the system may be configured to determine whether the data subject is contacted (e.g., via a phone call or email) by the one or more computer systems (e.g., automatically). In response to determining that the data subject has been contacted following submission of the form, the system may determine that the one or more computer systems have not fully deleted the data subject's personal data (e.g., because the one or more computer systems must still be storing contact information for the data subject in at least one location).

In particular embodiments, the system is configured to generate one or more test profiles for one or more test data subjects. For each of the one or more test data subjects, the system may be configured to generate and store test profile data such as, for example: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable test data. The system may then be configured to at least initially consent to processing or collection of personal data for the one or more test data subjects by the entity. The system may then request deletion, by the entity, of any personal data associated with a particular test data subject. In response to requesting the deletion of data for the particular test data subject, the system may then take one or more actions using the test profile data associated with the particular test data subjects in order to confirm that the one or more computers systems have, in fact, deleted the test data subject's personal data (e.g., any suitable action described herein). The system may, for example, be configured to: (1) initiate a contact request on behalf of the test data subject; (2) attempt to login to one or more user accounts that the system had created for the particular test data subject; and/or (3) take any other action, the effect of which could indicate a lack of complete deletion of the test data subject's personal data.

In response to determining that the one or more computer systems have not fully deleted a data subject's (or test data subject's) personal data, the system may then be configured, in particular embodiments, to: (1) flag the data subject's personal data for follow up by one or more privacy officers to investigate the lack of deletion; (2) perform one or more scans of one or more computing systems associated with the entity to identify any residual personal data that may be associated with the data subject; (3) generate a report indicating the lack of complete deletion; and/or (4) take any other suitable action to flag for follow-up the data subject, personal data, initial request to be forgotten, etc.

The system may, for example, be configured to test to ensure the data has been deleted by: (1) submitting a unique token of data through a form to a system (e.g., mark to); (2) in response to passage of an expected data retention time, test the system by calling into the system after the passage of the data retention time to search for the unique token. In response to finding the unique token, the system may be configured to determine that the data has not been properly deleted.

In various embodiments, a system may be configured to substantially automatically determine whether to take one or more actions in response to one or more identified risk triggers. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime). In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger.

In particular embodiments, the system may, for example, be configured to: (1) receive risk remediation data for a plurality of identified risk triggers from a plurality of different entities; (2) analyze the risk remediation data to determine a pattern in assigned risk levels and determined response to particular risk triggers; and (3) develop a model based on the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers.

In some embodiments, when a change or update is made to one or more processing activities and/or data assets (e.g., a database associated with a particular organization), the system may use data modeling techniques to update the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers. In various embodiments, when a privacy campaign, processing activity, etc. of the particular organization is modified (e.g., add, remove, or update particular information), then the system may use the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers.

In particular embodiments, the system may, for example, be configured to: (1) access risk remediation data for an entity that identifies one or more suitable actions to remediate a risk in response to identifying one or more data assets of the entity that may be affected by one or more potential risk triggers; (2) receive an indication of an update to the one or more data assets; (3) identify one or more potential updated risk triggers for an entity; (4) assess and analyze the one or more potential updated risk triggers to determine a relevance of a risk posed to the entity by the one or more potential updated risk triggers; (5) use one or more data modeling techniques to identify one or more data assets associated with the entity that may be affected by the risk; and (6) update the risk remediation data to include the one or more actions to remediate the risk in response to identifying the one or more potential updated risk triggers.

In any embodiment described herein, an automated classification system may be configured to substantially automatically classify one or more pieces of personal information in one or more documents (e.g., one or more text-based documents, one or more spreadsheets, one or more PDFs, one or more webpages, etc.). In particular embodiments, the system may be implemented in the context of any suitable privacy compliance system, which may, for example, be configured to calculate and assign a sensitivity score to a particular document based at least in part on one or more determined categories of personal information (e.g., personal data) identified in the one or more documents. As understood in the art, the storage of particular types of personal information may be governed by one or more government or industry regulations. As such, it may be desirable to implement one or more automated measures to automatically classify personal information from stored documents (e.g., to determine whether such documents may require particular security measures, storage techniques, handling, whether the documents should be destroyed, etc.).

Exemplary Technical Platforms

As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.

Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.

Example System Architecture

FIG. 1 is a block diagram of a data subject access request processing and fulfillment system 100 according to a particular embodiment. In various embodiments, the data subject access request processing and fulfillment system is part of a privacy compliance system (also referred to as a privacy management system), or other system, which may, for example, be associated with a particular organization and be configured to aid in compliance with one or more legal or industry regulations related to the collection and storage of personal data.

As may be understood from FIG. 1, the data subject access request processing and fulfillment system 100 includes one or more computer networks 115, a Data Model Generation Server 110, a Data Model Population Server 120, an Intelligent Identity Scanning Server 130 (which may automatically validate a DSAR requestor's identity), One or More Databases 140 or other data structures, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Third Party Servers 160. In particular embodiments, the one or more computer networks 115 facilitate communication between the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning/Verification Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170. Although in the embodiment shown in FIG. 1, the Data Model Generation Server 110, Data Model Population Server 120, Intelligent Identity Scanning Server 130, One or More Databases 140, one or more remote computing devices 150 (e.g., a desktop computer, laptop computer, tablet computer, smartphone, etc.), and One or More Third Party Servers 160, and DSAR Processing and Fulfillment Server 170 are shown as separate servers, it should be understood that in other embodiments, the functionality of one or more of these servers and/or computing devices may, in different embodiments, be executed by a larger or smaller number of local servers, one or more cloud-based servers, or any other suitable configuration of computers.

The one or more computer networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet, a private intranet, a public switch telephone network (PSTN), or any other type of network. The communication link between the DSAR Processing and Fulfillment Server 170 and the One or More Remote Computing Devices 150 may be, for example, implemented via a Local Area Network (LAN) or via the Internet. In other embodiments, the One or More Databases 140 may be stored either fully or partially on any suitable server or combination of servers described herein.

FIG. 2A illustrates a diagrammatic representation of a computer 200 that can be used within the data subject access request processing and fulfillment system 100, for example, as a client computer (e.g., one or more remote computing devices 150 shown in FIG. 1), or as a server computer (e.g., Data Model Generation Server 110 shown in FIG. 1). In particular embodiments, the computer 200 may be suitable for use as a computer within the context of the data subject access request processing and fulfillment system 100 that is configured for routing and/or processing DSAR requests and/or generating one or more data models used in automatically fulfilling those requests.

In particular embodiments, the computer 200 may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer 200 may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The Computer 200 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

An exemplary computer 200 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.

The processing device 202 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.

The computer 120 may further include a network interface device 208. The computer 200 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).

The data storage device 218 may include a non-transitory computer-accessible storage medium 230 (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software instructions 222) embodying any one or more of the methodologies or functions described herein. The software instructions 222 may also reside, completely or at least partially, within main memory 204 and/or within processing device 202 during execution thereof by computer 200—main memory 204 and processing device 202 also constituting computer-accessible storage media. The software instructions 222 may further be transmitted or received over a network 115 via network interface device 208.

While the computer-accessible storage medium 230 is shown in an exemplary embodiment to be a single medium, the term “computer-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The terms “computer-accessible storage medium”, “computer-readable medium”, and like terms should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. These terms should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.

Systems for Managing Data Subject Access Requests

In various embodiments, the system may include a ticket management system and/or other systems for managing data subject access requests. In operation, the system may use one or more computer processors, which are operatively coupled to memory, to execute one or more software modules (which may be included in the Instructions 222 referenced above) such as: (1) a DSAR Request Routing Module 1000; and (4) a DSAR Prioritization Module. An overview of the functionality and operation of each of these modules is provided below.

Data Subject Access Request Routing Module 1000

As shown in FIG. 2B, a Data Subject Access Request Routing Module 1000, according to particular embodiments, is adapted for executing the steps of: (1) at Step 1050, presenting, by at least one computer processor, a first webform on a first website, the first webform being adapted to receive data subject access requests and to route the requests to a first designated individual (e.g., an individual who is associated with a first sub-organization of a particular organization—e.g., an employee of the first sub-organization) for processing (in various embodiments, “presenting a webform on a website” may comprise, for example: (A) providing a button, link, or other selectable indicium on the website that, when selected, causes the system to display the webform, or (B) displaying the webform directly on the website); (2) at Step 1100 presenting, by at least one computer processor, a second webform on a second website, the second webform being adapted to receive data subject access requests and to route the requests to a second designated individual (e.g., an individual who is associated with a second sub-organization of a particular organization—e.g., an employee of the second sub-organization) for processing; (3) at Step 1150, receiving, by at least one computer processor, via the first webform, a first data subject access request; (4) at Step 1200, at least partially in response to the receiving the first data subject access request, automatically routing the first data subject access request to the first designated individual for handling; (5) at Step 1250, at least partially in response to the receiving the second data subject access request, automatically routing the second data subject access request to the second designated individual for handling; and (6) at Step 1300, communicating, via a single user interface, a status of both the first data subject access request and the second data subject access request.

In particular embodiments: (1) the first website is a website of a first sub-organization of a particular parent organization; (2) the second website is a website of a second sub-organization of the particular parent organization; and (3) the computer-implemented method further comprises communicating, by at least one computer processor, via a single user interface, a status of each of said first data subject access request and said second data subject access request (e.g., to an employee of—e.g., privacy officer of—the parent organization). As discussed in more detail below, this single user interface may display an indication, for each respective one of the first and second data subject access requests, of a number of days remaining until a deadline for fulfilling the respective data subject access request.

In certain embodiments, the single user interface is adapted to facilitate the deletion or assignment of multiple data subject access requests to a particular individual for handling in response to a single command from a user (e.g., in response to a user first selecting multiple data subject access requests from the single user interface and then executing an assign command to assign each of the multiple requests to a particular individual for handling).

In particular embodiments, the system running the Data Subject Access Request Routing Module 1000, according to particular embodiments, may be adapted for, in response to receiving each data subject access request, generating an ID number (e.g., a transaction ID or suitable Authentication Token) for the first data subject access request, which may be used later, by the DSAR requestor, to access information related to the DSAR, such as personal information requested via the DSAR, the status of the DSAR request, etc. To facilitate this, the system may be adapted for receiving the ID number from an individual and, at least partially in response to receiving the ID number from the individual, providing the individual with information regarding status of the data subject access request and/or information previously requested via the data subject access request.

In particular embodiments, the system may be adapted to facilitate the processing of multiple different types of data subject access requests. For example, the system may be adapted to facilitate processing: (1) requests for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) requests for all such personal data to be deleted; (3) requests to update personal data that the organization is storing for the data subject; (4) requests to opt out of having the organization use the individual's personal information in one or more particular ways (e.g., per the organization's standard business practices), or otherwise change the way that the organization uses the individual's personal information; and/or (5) the filing of complaints.

In particular embodiments, the system may execute one or more steps (e.g., any suitable step or steps discussed herein) automatically. For example, the system may be adapted for: (1) receiving, from the first designated individual, a request to extend a deadline for satisfying the first data subject access request; (2) at least partially in response to receiving the extension request, automatically determining, by at least one processor, whether the requested extension complies with one or more applicable laws or internal policies; and (3) at least partially in response to determining that the requested extension complies with the one or more applicable laws or internal policies, automatically modifying the deadline, in memory, to extend the deadline according to the extension request. The system may be further adapted for, at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically rejecting the extension request. In various embodiments, the system may also, or alternatively, be adapted for: (1) at least partially in response to determining that the requested extension does not comply with the one or more applicable laws or internal policies, automatically modifying the length of the requested extension to comply with the one or more applicable laws or internal policies; and (2) automatically modifying the deadline, in memory, to extend the deadline according to the extension request.

In various embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access requestor placing the first data subject access request; (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically obtaining, from a particular data model, at least a portion of information requested in the first data subject access request; and (3) after obtaining the at least a portion of the requested information, displaying the obtained information to a user as part of a fulfillment of the first data subject access request. The information requested in the first data subject access request may, for example, comprise at least substantially all (e.g., most or all) of the information regarding the first data subject that is stored within the data model.

In various embodiments, the system is adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically facilitating an update of personal data that an organization associated with the first webform is processing regarding the particular data subject access requestor.

Similarly, in particular embodiments, the system may be adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically processing a request, made by the particular data subject access requestor, to opt out of having the organization use the particular data subject access requestor's personal information in one or more particular ways.

The system may, in various embodiments, be adapted for: (1) providing, by at least one computer processor, a webform creation tool that is adapted for receiving webform creation criteria from a particular user, the webform creation criteria comprising at least one criterion from a group consisting of: (A) a language that the form will be displayed in; (B) what information is to be requested from data subjects who use the webform to initiate a data subject access request; and (C) who any data subject access requests that are received via the webform will be routed to; and (2) executing the webform creation tool to create both the first webform and the second webform.

In light of the discussion above, although the Data Subject Access Request Routing Module 1000 is described as being adapted to, in various embodiments, route data subject access requests to particular individuals for handling, it should be understood that, in particular embodiments, this module may be adapted to process at least part of, or all of, particular data subject access requests automatically (e.g., without input from a human user). In such cases, the system may or may not route such automatically-processed requests to a designated individual for additional handling or monitoring. In particular embodiments, the system may automatically fulfill all or a portion of a particular DSAR request, automatically assign a transaction ID and/or authentication token to the automatically fulfilled transaction, and then display the completed DSAR transaction for display on a system dashboard associated with a particular responsible individual that would otherwise have been responsible for processing the DSAR request (e.g., an individual to whom the a webform receiving the DSAR would otherwise route DSAR requests). This may be helpful in allowing the human user to later track, and answer any questions about, the automatically-fulfilled DSAR request.

It should also be understood that, although the system is described, in various embodiments, as receiving DSAR requests via multiple webforms, each of which is located on a different website, the system may, in other embodiments, receive requests via only a single webform, or through any other suitable input mechanism other than a webform (e.g., through any suitable software application, request via SMS message, request via email, data transfer via a suitable API, etc.)

In various embodiments, the system may be adapted to access information needed to satisfy DSAR requests via one or more suitable data models. Such data models include those that are described in greater detail in U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, which, as noted above, is incorporated herein by reference. In various embodiments, the system is adapted to build and access such data models as described in this earlier-filed U.S. patent application.

As an example, in fulfilling a request to produce, modify, or delete, any of a data subject's personal information that is stored by a particular entity, the system may be adapted to access a suitable data model to identify any personal data of the data subject that is currently being stored in one or more computer systems associated with the particular entity. After using the data model to identify the data, the system may automatically process the data accordingly (e.g., by modifying or deleting it, and/or sharing it with the DSAR requestor).

DSAR Prioritization Module

A DSAR Prioritization Module, according to various embodiments, is adapted for (1) executing the steps of receiving a data subject access request; (2) at least partially in response to receiving the data subject access request, obtaining metadata regarding a data subject of the data subject access request; (3) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (4) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

The operation of various embodiments of the various software modules above is described in greater detail below. It should be understood that the various steps described herein may be executed, by the system, in any suitable order and that various steps may be omitted, or other steps may be added in various embodiments.

Operation of Example Implementation

FIGS. 3-43 are screen shots that demonstrate the operation of a particular embodiment. FIGS. 3-6 show a graphical user interface (GUI) of an example webform construction tool. FIG. 3 shows a user working to design a webform called “Web_form_1”. As may be understood from the vertical menu shown on the left-hand side of the screen, the webform construction tool allows users to design a webform by: (1) specifying the details of the form (via the “Form Details” tab); (2) defining the fields that will be displayed on the webform (via the “Webform Fields” tab); (3) defining the styling of the webform (via the “Form Styling” tab); and (4) defining various settings associated with the webform (via the “Settings” tab). As shown in FIGS. 4-6, the user may also specify text to be displayed on the webform (e.g., via a “Form Text” tab).

FIG. 4 shows that, by selecting the “Form Details” tab, the user may define which answers a requestor will be able to specify on the webform in response to prompts for information regarding what type of individual they are (customer, employee, etc.) and what type of request they are making via the webform. Example request types include: (1) a request for all personal data that an organization is processing for the data subject (a copy of the personal data in a commonly used, machine-readable format); (2) a request for all such personal data to be deleted; (3) a request to update personal data that the organization is storing for the data subject; (4) a request to opt out of having the organization use the individual's personal information in one or more particular ways (e.g., per the organization's standard business practices); (5) file a complaint; and/or (6) other.

FIG. 5 shows that, by selecting the “Settings” tab, the user may specify various system settings, such as whether Captcha will be used to verify that information is being entered by a human, rather than a computer.

FIG. 6 shows that, by selecting the Form Styling tab, the user may specify the styling of the webform. The styling may include, for example: (1) a header logo; (2) header height; (3) header color; (4) body text color; (5) body text size; (6) form label color; (7) button color; (8) button text color; (9) footer text color; (10) footer text size; and/or any other suitable styling related to the webform.

In other embodiments, the system is configured to enable a user to specify, when configuring a new webform, what individual at a particular organization (e.g., company) will be responsible for responding to requests made via the webform. The system may, for example, enable the user to define a specific default sub-organization (e.g., within the organization) responsible for responding to DSAR's submitted via the new webform. As such, the system may be configured to automatically route a new DSAR made via the new webform to the appropriate sub-organization for processing and fulfillment. In various embodiments, the system is configured to route one or more various portions of the DSAR to one or more different sub-organizations within the organization for handling.

In particular embodiments, the system may include any suitable logic for determining how the webform routes data subject access requests. For example, the system may be adapted to determine which organization or individual to route a particular data subject access request to based, at least in part, on one or more factors selected from a group consisting of: (1) the data subject's current location; (2) the data subject's country of residence; (3) the type of request being made; (4) the type of systems that contain (e.g., store and/or process) the user's personal data (e.g., in ADP, Salesforce, etc.); or any other suitable factor.

In particular embodiments, the system is configured to enable a user generating webforms to assign multiple webforms to multiple different respective suborganizations within an organization. For example, an organization called ACME, Inc. may have a website for each of a plurality of different brands (e.g., sub-organizations) under which ACME sells products (e.g., UNICORN Brand T-shirts, GRIPP Brand Jeans, etc.). As may be understood in light of this disclosure, each website for each of the particular brands may include an associated webform for submitting DSAR's (either a webform directly on the web site, or one that is accessible via a link on the website). Each respective webform may be configured to route a DSAR made via its associated brand website to a particular sub-organization and/or individuals within ACME for handling DSAR's related to the brand.

As noted above, after the user uses the webform construction tool to design a particular webform for use on a particular web page, the webform construction tool generates code (e.g., HTML code) that may be pasted into the particular web page to run the designed webform page. In particular embodiment, when pasted into the particular web page, the code generates a selectable button on the web page that, when selected, causes the system to display a suitable DSAR request webform.

FIG. 7 shows the privacy webpage of a company (e.g., the ACME corporation). As shown in this figure, a requestor may submit a DSAR by selecting a “Submit a Privacy Related Request” button on the web page.

FIG. 8 shows a webform that is displayed after a requestor selects the “Submit a Privacy Related Request” button on the privacy webpage of FIG. 7. As may be understood from this figure, the requestor may complete the webform by specifying which type of user they are, and what type of request they are making. The webform also asks the requestor to provide enough personal information to confirm their identity (e.g., and fulfill the request). As shown in this figure, the system may prompt a user submitting a DSAR to provide information for the user such as, for example: (1) what type of requestor the user is (e.g., employee, customer, etc.); (2) what the request involves (e.g., requesting info, opting out, deleting data, updating data, etc.); (3) first name; (4) last name; (5) email address; (6) telephone number; (7) home address; (8) one or more other pieces of identifying information; and/or (9) one or more details associated with the request. FIG. 9 shows an example populated version of the webform.

As shown in FIG. 10, after a requestor completes the webform and selects a “submit” indicia, the system displays a message to the requestor indicating that their DSAR has been successfully submitted. The system also displays a Request ID associated with the request. In response to the requestor successfully submitting the request, the system may also send an email (or other suitable communication) to the requestor confirming the request. An example of a suitable confirmation email is shown in FIG. 11.

In various embodiments, the system includes a dashboard that may be used by various individuals within an organization (e.g., one or more privacy officers of an organization) to manage multiple DSAR requests. As discussed above, the dashboard may display DSAR's submitted, respectively, to a single organization, any of multiple different sub-organizations (divisions, departments, subsidiaries etc.) of a particular organization, and/or any of multiple independent organizations. For example, the dashboard may display a listing of DSAR's that were submitted from a parent organization and from the parent organization's U.S. and European subsidiaries. This may be advantageous, for example, because it may allow an organization to manage all DSAR requests of all of its sub-organizations (and/or other related organizations) centrally.

FIGS. 12-23, 25-27, 29-34, and 41-43 depict various example user-interface screens of a DSAR request-management dashboard. As may be understood from FIG. 12, after an appropriate user (e.g., a privacy officer associated with a particular organization) logs into the system, the system may display a Data Subject Request Queue that may, for example, display a listing of all data subject access requests that the appropriate individual has been designated to process. As shown in FIG. 12, each data subject access request may be represented by a respective row of information that includes: (1) an ID number for the request; (2) the name of the data subject who has submitted the request; (3) the status of the request; (4) the number of days that are left to respond to the request (e.g., according to applicable laws and/or internal procedures); (5) an indication as to whether the deadline to respond to the request has been extended; (6) a creation date of the request; (7) an indication of the type of requestor that submitted the request (customer, employee, etc.); (8) the name of the individual who has been assigned to process the request (e.g., the respondent). This screen may also include selectable “Edit” and “Filter” buttons that respectively facilitate acting on and filtering the various requests displayed on the page.

As shown in FIG. 13, in response to a respondent selecting the edit button while a particular DSAR is highlighted, the system displays a dropdown menu allowing the respondent to select between taking the following actions: (1) verify the request; (2) assign the request to another individual; (3) request an extension; (4) reject the request; or (5) suspend the request.

FIGS. 14 and 15 show a message that the system displays to the respondent in response to the respondent selecting the “verify” option. As shown in this figure, the system prompts the respondent to indicate whether they are sure that they wish to authenticate the request. The system also presents an input field where the respondent can enter text to be displayed to the requestor along with a request for the requestor to provide information verifying that they are the data subject associated with the request. After the respondent populates the input field, they may submit the request by selecting a “Submit” button.

In particular embodiments, the input field may enable the respondent to provide one or more supporting reasons for a decision, by the respondent, to authenticate the request. The respondent may also upload one or more supporting documents (such as an attachment). The supporting documents or information may include, for example, one or more documents utilized in confirming the requestor's identity, etc.

In response to the respondent selecting the Submit button, the system changes the status of the request to “In Progress” and also changes the color of the request's status from orange to blue (or from any other suitable color to any different suitable color)—see FIG. 16. The system also generates and sends a message (e.g., an electronic or paper message) to the requestor asking them to submit information verifying the request. The message may include the text that the respondent entered in the text box of FIG. 14.

As shown in FIGS. 17-19, in response to a respondent selecting the “Edit” button and then selecting the “Assign” indicia from the displayed dropdown menu, the system displays a Request Assignment interface that allows a respondent to indicate who the request should be assigned to. For example, the respondent may indicate that they will be handling the request, or assign the request to another suitable individual, who may, for example, then be designated as the respondent for the request. If the respondent assigns the request to another individual for handling, the respondent may also provide an email address or other correspondence information for the individual. The Request Assignment interface includes a comment box for allowing a respondent to add a message to the individual that the assignment will be assigned to regarding the assignment. In response to the respondent selecting the “Assign” button, the system assigns the request to the designated individual for handling. If the request has been assigned to another, designated individual, the system automatically generates and sends a message (e.g., an electronic message such as an email or SMS message) to the designated individual informing them of the assignment.

As shown in FIGS. 20-22, in response to a respondent selecting the “Edit” button and then selecting the “Reject” indicia from the displayed dropdown menu, the system displays a Reject Request interface. This interface includes a comment box for allowing a respondent to add a message to the requestor as to why the request was rejected. In response to the respondent selecting the “Submit” button, the system changes the status of the request to “Rejected” and changes the color of the request's status indicator to red (See FIG. 23). The system may also automatically generate a message (e.g., an electronic or paper message) to the requestor notifying them that their request has been rejected and displaying the text that the respondent entered into the Reject Request interface of FIG. 22. An example of such a message is shown in FIG. 24.

As shown in FIGS. 25-26, in response to a respondent selecting the “Edit” button and then selecting the “Request Extension” indicia from the displayed dropdown menu, the system displays a Request Extension interface. This includes a text box for allowing a user to indicate the number of days for which they would like to extend the current deadline for responding to the request. For example, the dialog box of FIG. 26 shows the respondent requesting that the current deadline be extended by 90 days. In response to the respondent entering a desired extension duration and selecting the “Submit” button, the system updates the deadline in the system's memory (e.g., in an appropriate data structure) to reflect the extension. For instance, in the example of FIG. 26, the system extends the deadline to be 90 days later than the current deadline. As shown in FIG. 27, the system also updates the “Days Left to Respond” field within the Data Subject Request Queue to reflect the extension (e.g., from 2 days from the current date to 92 days from the current date). As shown in FIG. 28, the system may also generate an appropriate message (e.g., an electronic, such as an email, or a paper message) to the requestor indicating that the request has been delayed. This message may provide a reason for the delay and/or an anticipated updated completion date for the request.

In particular embodiments, the system may include logic for automatically determining whether a requested extension complies with one or more applicable laws or internal policies and, in response, either automatically grant or reject the requested extension. For example, if the maximum allowable time for replying to a particular request is 90 days under the controlling laws and the respondent requests an extension that would result in the fulfillment of the request 91 or more days from the date that the request was submitted, the system may automatically reject the extension request. In various embodiments, the system may also communicate, to the respondent (e.g., via a suitable electronic message or text display on a system user interface) an explanation as to why the extension request was denied, and/or a maximum amount of time (e.g., a maximum number of days) that the deadline may be extended under the applicable laws or policies. In various embodiments, if the system determines that the requested extension is permissible under the applicable laws and/or policies, the system may automatically grant the extension.

In other embodiments, the system may be configured to automatically modify a length of the requested extension to conform with one or more applicable laws and/or policies. For example, if the request was for a 90-day extension, but only a 60 day extension is available under the applicable laws or regulations, the system may automatically grant a 60-day extension rather than a 90 day extension. The system may be adapted to also automatically generate and transmit a suitable message (e.g., a suitable electronic or paper communication) notifying them of the fact that the extension was granted for a shorter, specified period of time than requested.

As shown in FIGS. 29-34, a respondent may obtain additional details regarding a particular request by selecting (e.g., clicking on) the request on the Data Subject Request Queue screen. For example, FIG. 30 shows a Data Subject Request Details screen that the system displays in response to a respondent selecting the “Donald Blair” request on the user interface screen of FIG. 35. As shown in FIG. 30, the Data Subject Request Details screen shows all correspondence between the organization and the requesting individual regarding the selected data subject access request. As may be understood from FIG. 31, when a respondent selects a particular correspondence (e.g., email), the system displays the correspondence to the respondent for review or other processing.

As shown in FIG. 32, in various embodiments, the system may provide a selectable “Reply” indicia that allows the respondent to reply to particular correspondence from an individual. As may be understood from this figure, in response to the respondent selecting the “Reply” indicia, the system may display a dropdown menu of various standard replies. For example, the dropdown menu may provide the option of generating a reply to the requestor indicating that the request has been rejected, is pending, has been extended, or that the request has been completed.

As shown in FIG. 33, in response to the respondent selecting “Reply as Completed”, the system may generate a draft email to the requestor explaining that the request has been completed. The respondent may then edit this email and send the edited correspondence (e.g., via email) to the requestor by selecting a “Send as Complete” indicia. As shown in FIG. 34, the system may, in response, display an indicator adjacent the correspondence indicating that the correspondence included a reply indicating that the request was complete. This may be useful in allowing individuals to understand the contents of the correspondence without having to open it.

FIG. 35 shows an example email automatically generated by the system in response to the respondent selecting “Reply as Completed” on the screen shown in FIG. 32. As shown in FIG. 35, the correspondence may include a secure link that the requestor may select to access the data that was requested in the DSAR. In particular embodiments, the link is a link to a secure website, such as the website shown in FIG. 36, that provides access to the requested data (e.g., by allowing a user to download a .pdf file, or other suitable file, that includes the requested data). As shown in FIG. 36, the website may require multiple pieces of data to verify that the requestor is permitted to access the site. For example, in order to access the website, the requestor may be required to provide both the unique ID number of the request, and an authentication token, which the system may send to the user via email—See FIGS. 37 and 38.

FIGS. 39-43 are computer screen shots that depict additional user interfaces according to various embodiments.

Additional Concepts

Intelligent Prioritization of DSAR's

In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.

Examples of metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of request, (2) the location from which the request is being made, (3) current sensitivities to world events, (4) a status of the requestor (e.g., especially loyal customer), or (5) any other suitable metadata.

In various embodiments, in response to the system determining that the priority of a particular DSAR should be elevated, the system may automatically adjust the deadline for responding to the DSAR. For example, the system may update the deadline in the system's memory and/or modify the “Days Left to Respond” field (See FIG. 13) to include a fewer number of days left to respond to the request. Alternatively, or in addition, the system may use other techniques to convey to a respondent that the request should be expedited (e.g., change the color of the request, send a message to the respondent that they should process the request before non-prioritized requests, etc.)

In various embodiments, in response to the system determining that the priority of a particular DSAR should be lowered, the system may automatically adjust the deadline for responding to the DSAR by adding to the number of days left to respond to the request.

Automatic Deletion of Data Subject Records Based on Detected Systems

In particular embodiments, in response a data subject submitting a request to delete their personal data from an organization's systems, the system may: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., and deleting a directory entry associated with the data); and/or (3) any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system uses an appropriate data model (see discussion above) to efficiently determine where all of the data subject's personal data is stored.

Automatic Determination of Business Processes that Increase Chance of Deletion Requests

In various embodiments, the system is adapted to store, in memory, a log of DSAR actions. The system may also store, in memory, additional information regarding the data subjects of each of the requests. The system may use this information, for example, to determine which business processes are most commonly associated with a data subject submitting a request to have their personal information deleted from the organization's systems. The organization may then use this information to revise the identified business processes in an effort to reduce the number of deletion requests issued by data subjects associated with the business processes.

As a particular example, the system may analyze stored information to determine that a high number (e.g., 15%) of all participants in a company's loyalty program submit requests to have their personal information deleted from the company's systems. In response to making this determination, the system may issue an electronic alert to an appropriate individual (e.g., a privacy officer of the company), informing them of the high rate of members of the company's loyalty program issuing personal data delete requests. This alert may prompt the individual to research the issue and try to resolve it.

Automated Data Subject Verification

In various embodiments, before a data subject request can be processed, the data subject's identity may need to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of Data Subject Access Request being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of data to verify authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.

Stated more particularly, when processing a data subject access request, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step). In various embodiments, confirming the identity of the data subject may, for example, limit a risk that a third-party or other entity may gain unlawful or unconsented to access to the requestor's personal data. The system may, for example, limit processing and fulfillment of requests relating to a particular data subject to requests that are originated by (e.g., received from) the particular data subject. When processing a data subject access request, the system may be configured to use various reasonable measures to verify the identity of the data subject who requests access (e.g., in particular in the context of online services and online identifiers). In particular embodiments, the system is configured to substantially automatically validate an identity of a data subject when processing the data subject access request.

For example, in particular embodiments, the system may be configured to substantially automatically (e.g., automatically) authenticate and/or validate an identity of a data subject using any suitable technique. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business data subject access request); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) etc. Various exemplary techniques for authenticating a data subject are discussed more fully below.

In particular embodiments, when authenticating a data subject (e.g., validating the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when validating a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the data subject access request) actually exists. In various embodiments, the system is configured to interface with (e.g., transmit a search request to) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to confirm that a person with one or more characteristics provided by the data subject exists. The system may, for example, interface with such credit reporting agencies via a suitable plugin (e.g., software plugin). Additionally, there might be a verification on behalf of a trusted third-party system (e.g., the controller).

In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, IDology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. The system may be configured to interface with one or more such third-party systems to confirm that a person with one or more characteristics provided by the data subject exists.

After the step of confirming the existence of a person with the one or more characteristics provided by the data subject, the system may be configured to confirm that the person making the data subject access request is, in fact, the data subject. The system may, for example, verify that the requestor is the data subject by prompting the requestor to answer one or more knowledge-based authentication questions (e.g., out-of-wallet questions). In particular embodiments, the system is configured to utilize one or more third-party services as a source of such questions (e.g., any of the suitable third-party sources discussed immediately above). The system may use third-party data from the one or more third-party sources to generate one or more questions. These one or more questions may include questions that a data subject should know an answer to without knowing the question ahead of time (e.g., one or more previous addresses, a parent or spouse name and/or maiden name, etc.).

FIG. 46 depicts an exemplary identity verification questionnaire. As may be understood from this figure, an identity verification questionnaire may include one or more questions whose responses include data that the system may derive from one or more credit agencies or other third-party data aggregation services (e.g., such as previous street addresses, close associates, previous cities lived in, etc.). In particular embodiments, the system is configured to provide these one or more questions to the data subject in response to receiving the data subject access request. In other embodiments, the system is configured to prompt the data subject to provide responses to the one or more questions at a later time (e.g., during processing of the request). In particular other embodiments, the system is configured to substantially automatically compare one or more pieces of information provided as part of the data subject access request to one or more pieces of data received from a third-party data aggregation service in order to substantially automatically verify the requestor's identity.

In still other embodiments, the system may be configured to prompt a requestor to provide one or more additional pieces of information in order to validate the requestor's identity. This information may include, for example: (1) at least a portion of the requestor's social security number (e.g., last four digits); (2) a name and/or place of birth of the requestor's father; (3) a name, maiden name, and/or place of birth of the requestor's mother; and/or (4) any other information which may be useful for confirming the requestor's identity (e.g., such as information available on the requestor's birth certificate). In other embodiments, the system may be configured to prompt the requestor to provide authorization for the company to check the requestor's social security or other private records (e.g., credit check authorization, etc.) to obtain information that the system may use to confirm the requestor's identity. In other embodiments, the system may prompt the user to provide one or more images (e.g., using a suitable mobile computing device) of an identifying document (e.g., a birth certificate, social security card, driver's license, etc.).

The system may, in response to a user providing one or more responses that matches information that the system receives from one or more third-party data aggregators or through any other suitable background, credit, or other search, substantially automatically authenticate the requestor as the data subject. The system may then continue processing the data subject's request, and ultimately fulfill their request.

In particular embodiments, such as embodiments in which the requestor includes a business (e.g., as in a business to business data subject access request), the system may be configured to authenticate the requesting business using one or more company verification techniques. These one or more company validation techniques may include, for example, validating a vendor contract (e.g., between the requesting business and the company receiving the data subject access request); receiving a matching token, code, or other unique identifier provided by the company receiving the data subject access request to the requesting business; receiving a matching file in possession of both the requesting business and the company receiving the data subject access request; receiving a signed contract, certificate (e.g., digital or physical), or other document memorializing an association between the requesting business and the company receiving the data subject access request; and/or any other suitable method of validating that a particular request is actually made on behalf of the requesting business (e.g., by requesting the requesting business to provide one or more pieces of information, one or more files, one or more documents, etc. that may only be accessible to the requesting business).

In other embodiments, the system may be configured to authenticate a request via integration with a company's employee or customer (e.g., consumer) authentication process. For example, in response to receiving a data subject access request that indicates that the data subject is an employee of the company receiving the data subject access request, the system may be configured to prompt the employee to login to the company's employee authentication system (e.g., Okta, Azure, AD, etc.) In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. Similarly, in response to receiving a data subject access request that indicates that the data subject is a customer of the company receiving the data subject access request, the system may be configured to prompt the customer to login to an account associated with the company (e.g., via a consumer portal authentication process). In a particular example, this may include, for example, an Apple ID (for data subject access requests received by Apple). In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. In some embodiments, the system may be configured to require the requestor to login using two-factor authentication or other suitable existing employee or consumer authentication process.

Data Subject Blacklist

In various embodiments, a particular organization may not be required to respond to a data subject access request that originates (e.g., is received from) a malicious requestor. A malicious requestor may include, for example: (1) a requestor (e.g., an individual) that submits excessive or redundant data subject access requests; (2) a group of requestors such as researchers, professors, students, NGOs, etc. that submit a plurality of requests for reasons other than those reasons provided by policy, law, etc.; (3) a competitor of the company receiving the data subject access request that is submitting such requests to tie up the company's resources unnecessarily; (4) a terrorist or other organization that may spam requests to disrupt the company's operation and response to valid requests; and/or (5) any other request that may fall outside the scope of valid requests made for reasons proscribed by public policy, company policy, or law. In particular embodiments, the system is configured to maintain a blacklist of such malicious requestors.

In particular embodiments, the system is configured to track a source of each data subject access request and analyze each source to identify sources from which: (1) the company receives a large volume of requests; (2) the company receives a large number of repeat requests; (3) etc. These sources may include, for example: (1) one or more particular IP addresses; (2) one or more particular domains; (3) one or more particular countries; (4) one or more particular institutions; (5) one or more particular geographic regions; (6) etc. In various embodiments, in response to analyzing the sources of the requests, the system may identify one or more sources that may be malicious (e.g., are submitting excessive requests).

In various embodiments, the system is configured to maintain a database of the identified one or more sources (e.g., in computer memory). In particular embodiments, the database may store a listing of identities, data sources, etc. that have been blacklisted (e.g., by the system). In particular embodiments, the system is configured to, in response to receiving a new data subject access request, cross reference the request with the blacklist to determine if the requestor is on the blacklist or is making the request from a blacklisted source. The system may then, in response to determining that the requestor or source is blacklisted, substantially automatically reject the request. In particular embodiments, the blacklist cross-referencing step may be part of the requestor authentication (e.g., verification) discussed above. In various embodiments, the system may be configured to analyze request data on a company by company basis to generate a blacklist. In other embodiments, the system may analyze global data (e.g., all data collected for a plurality of companies that utilize the data subject access request fulfillment system) to generate the blacklist.

In particular embodiments, the system may be configured to fulfill data subject access requests for the purpose of providing a data subject with information regarding what data the company collects and for what purpose, for example, so the data subject can ensure that the company is collecting data for lawful reasons. As such, the system may be configured to identify requestors and other sources of data requests that are made for other reasons (e.g., one or more reasons that would not obligate the company to respond to the request). These reasons may include, for example, malicious or other reasons such as: (1) research by an academic institution by one or more students or professors; (2) anticompetitive requests by one or more competitors; (3) requests by disgruntled former employees for nefarious reasons; (4) etc.

In particular embodiments, the system may, for example, maintain a database (e.g., in computer memory) of former employees. In other embodiments, the system may, for example: (1) identify a plurality of IP addresses associated with a particular entity (e.g., academic organization, competitor, etc.); and (2) substantially automatically reject a data subject access request that originates from the plurality of IP addresses. In such embodiments, the system may be configured to automatically add such identified IP addresses and/or domains to the blacklist.

In still other embodiments, the system is configured to maintain a listing of blacklisted names of particular individuals. These may include, for example, one or more individuals identified (e.g., by an organization or other entity) as submitting malicious data subject access requests).

FIG. 47 depicts a queue of pending data subject access requests. As shown in this figure, the first three listed data subject access requests are new and require verification before processing and fulfillment can begin. As shown in this figure, a user (e.g., such as a privacy officer or other privacy controller) may select a particular request, and select an indicia for verifying the request. The user may also optionally select to reject the request. FIG. 48 depicts an authentication window that enables the user to authenticate a particular request. In various embodiments, the user may provide an explanation of why the user is authenticating the request (e.g., because the requestor successfully completed on or more out-of-wallet questions or for any other suitable reason). The user may further submit one or more attachments to support the verification. In this way, the system may be configured to document that the authentication process was performed for each request (e.g., in case there was an issue with improperly fulfilling a request, the company could show that they are following procedures to prevent such improper processing). In other embodiments, the system may enable the user to provide similar support when rejecting a request (e.g., because the requestor was blacklisted, made excessive requests, etc.).

Data Subject Access Request Fulfillment Cost Determination

In various embodiments, as may be understood in light of this disclosure, fulfilling a data subject access request may be particularly costly. In some embodiments, a company may store data regarding a particular data subject in multiple different locations for a plurality of different reasons as part of a plurality of different processing and other business activities. For example, a particular data subject may be both a customer and an employee of a particular company or organization. Accordingly, in some embodiments, fulfilling a data subject access request for a particular data subject may involve a plurality of different information technology (IT) professionals in a plurality of different departments of a particular company or organization. As such, it may be useful to determine a cost of a particular data subject access request (e.g., particularly because, in some cases, a data subject is entitled to a response to their data subject access request as a matter of right at no charge).

In particular embodiments, in response to receiving a data subject access request, the system may be configured to: (1) assign the request to at least one privacy team member; (2) identify one or more IT teams required to fulfill the request (e.g., one or more IT teams associated with one or more business units that may store personal data related to the request); (3) delegate one or more subtasks of the request to each of the one or more IT teams; (4) receive one or more time logs from each individual involved in the processing and fulfillment of the data subject access request; (5) calculate an effective rate of each individual's time (e.g., based at least in part on the individual's salary, bonus, benefits, chair cost, etc.); (6) calculate an effective cost of fulfilling the data subject access request based at least in part on the one or more time logs and effective rate of each of the individual's time; and (7) apply an adjustment to the calculated effective cost that accounts for one or more external factors (e.g., overhead, etc.) in order to calculate a cost of fulfilling the data subject access request.

In particular embodiments, the system is configured to substantially automatically track an amount of time spent by each individual involved in the processing and fulfillment of the data subject access request. The system may, for example, automatically track an amount of time between each individual opening and closing a ticket assigned to them as part of their role in processing or fulfilling the data subject access request. In other embodiments, the system may determine the time spent based on an amount of time provided by each respective individual (e.g., the individual may track their own time and submit it to the system).

In various embodiments, the system is configured to measure a cost of each particular data subject access request received, and analyze one or more trends in costs of, for example: (1) data subject access requests over time; (2) related data subject access requests; (3) etc. For example, the system may be configured to track and analyze cost and time-to-process trends for one or more social groups, one or more political groups, one or more class action groups, etc. In particular, the system may be configured to identify a particular group from which the system receives particularly costly data subject access request (e.g., former and/or current employees, members of a particular social group, members of a particular political group, etc.).

In particular embodiments, the system may be configured to utilize data subject access request cost data when processing, assigning, and/or fulfilling future data subject access requests (e.g., from a particular identified group, individual, etc.). For example, the system may be configured to prioritize requests that are expected to be less costly and time-consuming (e.g., based on past cost data) over requests identified as being likely more expensive. Alternatively, the system may prioritize more costly and time-consuming requests over less costly ones in the interest of ensuring that the system is able to respond to each request in a reasonable amount of time (e.g., within a time required by law, such as a thirty day period, or any other suitable time period).

Customer Satisfaction Integration with Data Subject Access Requests

In various embodiments, the system may be configured to collect customer satisfaction data, for example: (1) as part of a data subject access request submission form; (2) when providing one or more results of a data subject access request to the data subject; or (3) at any other suitable time. In various embodiments, the customer satisfaction data may be collected in the form of a suitable survey, free-form response questionnaire, or other suitable satisfaction data collection format (e.g., thumbs up vs. thumbs down, etc.).

FIG. 49 depicts an exemplary customer satisfaction survey that may be included as part of a data subject access request form, provided along with the results of a data subject access request, provided in one or more messages confirming receipt of a data subject access request, etc. As shown in the figure, the customer satisfaction survey may relate to how likely a customer (e.g., a data subject) is to recommend the company (e.g., to which the data subject has submitted the request) to a friend (e.g., or colleague). In the example shown in FIG. 49, the satisfaction survey may relate to a Net Promoter score (NPS), which may indicate a loyalty of a company's customer relationships. Generally speaking, the Net Promoter Score may measure a loyalty that exists between a provider and a consumer. In various embodiments, the provider may include a company, employer, or any other entity. In particular embodiments, the consumer may include a customer, employee, or other respondent to an NPS survey.

In particular embodiments, the question depicted in FIG. 49 is the primary question utilized in calculating a Net Promoter Score (e.g., “how likely is it that you would recommend our company/product/service to a friend or colleague?”). In particular embodiments, the question is presented with responses ranging from 0 (not at all likely) to 10 (extremely likely). In particular embodiments, the question may include any other suitable scale. As may be understood from FIG. 49, the system may be configured to assign particular categories to particular ratings on the 10 point scale. The system may be configured to track and store responses provided by consumers and calculate an overall NPS score for the provider. The system may be further configured to generate a visual representation of the NPS score, including a total number of responses received for each particular score and category as shown in FIG. 49.

In various embodiments, the system may be configured to measure data related to any other suitable customer satisfaction method (e.g., in addition to NPS). By integrating a customer satisfaction survey with the data subject access request process, the system may increase a number of consumers that provide one or more responses to the customer satisfaction survey. In particular embodiments, the system is configured to require the requestor to respond to the customer satisfaction survey prior to submitting the data subject access request.

Identifying and Deleting Orphaned Data

In particular embodiments, an Orphaned Data Action System is configured to analyze one or more data systems (e.g., data assets), identify one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization, and notify one or more individuals of the particular organization of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with one or more privacy campaigns of the particular organization. In various embodiments, one or more processes described herein with respect to the orphaned data action system may be performed by any suitable server, computer, and/or combination of servers and computers.

Various processes performed by the Orphaned Data Action System may be implemented by an Orphaned Data Action Module 5000. Referring to FIG. 50, in particular embodiments, the system, when executing the Orphaned Data Action Module 5000, is configured to: (1) access one or more data assets of a particular organization; (2) scan the one or more data assets to generate a catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals; (3) store the generated catalog in computer memory; (4) scan one or more data assets based at least in part on the generated catalog to identify a first portion of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with the one or more privacy campaigns; (5) generate an indication that the first portion of one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular organization is to be removed from the one or more data assets; (6) present the indication to one or more individuals associated with the particular organization; and (7) remove the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular organization from the one or more data assets.

When executing the Orphaned Data Action Module 5000, the system begins, at Step S010, by accessing one or more data systems associated with the particular entity. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, a data asset may include any software or device utilized by a particular entity for data collection, processing, transfer, storage, etc.

In particular embodiments, the system is configured to identify and access the one or more data assets using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset; (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) of data assets associated with a particular entity to identify and access the one or more data assets associated with the particular entity.

Continuing to Step S020, the system is configured to scan the one or more data assets to generate a catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals. The catalog may include a table of the one or more privacy campaigns within the data assets of the particular entity and, for each privacy campaign, the one or more pieces of personal data stored within the data assets of the particular entity that are associated with the particular privacy campaign. In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some implementations, the system may access, via one or more computer networks, one or more data models that map an association between one or more pieces of personal data stored within one or more data assets of the particular entity and one or more privacy campaigns of the particular entity. As further described herein, the data models may access the data assets of the particular entity and use one or more suitable data mapping techniques to link, or otherwise associate, the one or more pieces of personal data stored within one or more data assets of the particular entity and one or more privacy campaigns of the particular entity. In some implementations, the one or more data models may link, or otherwise associate, a particular individual and each piece of personal data of that particular individual that is stored on one or more data assets of the particular entity.

In some embodiments, the system is configured to generate and populate a data model based at least in part on existing information stored by the system (e.g., in one or more data assets), for example, using one or more suitable scanning techniques. In still other embodiments, the system is configured to access an existing data model that maps personal data stored by one or more organization systems to particular associated processing activities. In some implementations, the system is configured to generate and populate a data model substantially on the fly (e.g., as the system receives new data associated with particular processing activities). For example, a particular processing activity (e.g., privacy campaign) may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). A data model may locate the collected and stored email addresses for customers that elected to receive (e.g., consented to receipt of) the promotional email within the data assets of the particular entity, and then map each of the stored email addresses to the particular processing activity (i.e., the transmission of a periodic advertising e-mail) within the data assets of the particular entity.

Next, at Step S030, the system is configured to store the generated catalog of one or more privacy campaigns and one or more pieces of personal information associated with one or more individuals. In some implementations, the system may receive an indication that a new processing activity (e.g., privacy campaign) has been launched by the particular entity. In response to receiving the indication, the system may modify the one or more data models to map an association between (i) one or more pieces of personal data associated with one or more individuals obtained in connection with the new privacy campaign and (ii) the new privacy campaign initiated by the particular entity. As the system receives one or more pieces of personal data associated with one or more individuals (e.g., an email address signing up to receive information from the particular entity), then the data model associated with the particular processing activity may associate the received personal data with the privacy campaign. In some implementations, one or more data assets may already include the particular personal data (e.g., email address) because the particular individual, for example, previously provided their email address in relation to a different privacy campaign of the particular entity. In response, the system may access the particular personal data and associate that particular personal data with the new privacy campaign.

At Step S040, the system is configured to scan one or more data assets based at least in part on the generated catalog to identify a first portion of the one or more pieces of personal data that are one or more pieces of personal data that are not associated with the one or more privacy campaigns. In various embodiments, the system may use the generated catalogue to scan the data assets of the particular entity to identify personal data that has been collected and stored using one or more computer systems operated and/or utilized by a particular organization where the personal data is not currently being used as part of any privacy campaigns, processing activities, etc. undertaken by the particular organization. The one or more pieces of personal data that are not associated with the one or more privacy campaigns may be a portion of the personal data that is stored by the particular entity. In some implementations, the system may analyze the data models to identify the one or more pieces of personal data that are not associated with the one or more privacy campaigns.

When the particular privacy campaign, processing activity, etc. is terminated or otherwise discontinued, the system may determine if any of the associated personal data that has been collected and stored by the particular organization is now orphaned data. In some implementations, in response to the termination of a particular privacy campaign and/or processing activity, (e.g., manually or automatically), the system may be configured to scan one or more data assets based at least in part on the generated catalog or analyze the data models to determine whether any of the personal data that has been collected and stored by the particular organization is now orphaned data (e.g., whether any personal data collected and stored as part of the now-terminated privacy campaign is being utilized by any other processing activity, has some other legal basis for its continued storage, etc.). In some implementations, the system may generate an indication that one or more pieces of personal data that are associated with the terminated one or more privacy campaigns are included in the portion of the one or more pieces of personal data (e.g., orphaned data).

In additional implementations, the system may determine that a particular privacy campaign, processing activity, etc. has not been utilized for a period of time (e.g., a day, a month, a year). In response, the system may be configured to terminate the particular processing activity, processing activity, etc. In some implementations, in response to the system determining that a particular processing activity has not been utilized for a period of time, the system may prompt one or more individuals associated with the particular entity to indicate whether the particular privacy campaign should be terminated or otherwise discontinued.

For example, a particular processing activity may include transmission of a periodic advertising e-mail for a particular company (e.g., a hardware store). As part of the processing activity, the particular company may have collected and stored e-mail addresses for customers that elected to receive (e.g., consented to the receipt of) the promotional e-mails. In response to determining that the particular company has not sent out any promotional e-mails for at least a particular amount of time (e.g., for at least a particular number of months), the system may be configured to: (1) automatically terminate the processing activity; (2) identify any of the personal data collected as part of the processing activity that is now orphaned data (e.g., the e-mail addresses); and (3) automatically delete the identified orphaned data. The processing activity may have ended for any suitable reason (e.g., because the promotion that drove the periodic e-mails has ended). As may be understood in light of this disclosure, because the particular organization no longer has a valid basis for continuing to store the e-mail addresses of the customers once the e-mail addresses are no longer being used to send promotional e-mails, the organization may wish to substantially automate the removal of personal data stored in its computer systems that may place the organization in violation of one or more personal data storage rules or regulations.

Continuing to Step S050, the system is configured to generate an indication that the portion of one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular entity is to be removed from the one or more data assets. At Step S060, the system is configured to present the indication to one or more individuals associated with the particular entity. The indication may be an electronic notification to be provided to an individual (e.g., privacy officer) associated with the particular entity. The electronic notification may be, for example, (1) a notification within a software application (e.g., a data management system for the one or more data assets of the particular entity), (2) an email notification, (3) etc.

In some implementations, the indication may enable the individual (e.g., privacy officer of the particular entity) to select a set of the one or more pieces of personal data of the portion of the one or more pieces of personal data to retain based on one or more bases to retain the set of the one or more pieces of personal data.

In particular embodiments, the system may prompt the one or more individuals to provide one or more bases to retain the first set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns. In some implementations, in response to receiving the provided one or more valid bases to retain the first set of the one or more pieces of personal data from the one or more individuals associated with the particular entity, submitting the provided one or more valid bases to retain the first set of the one or more pieces of personal data to one or more second individuals associated with the particular entity for authorization. In response, the system may retain the first set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data from the one or more individuals associated with the particular entity. Further, the system may remove a second set of the one or more pieces of personal data of the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns from the one or more data assets. In particular embodiments, the second set of the one or more pieces of personal data may be different from the first set of the one or more pieces of personal data.

Continuing to Step S070, the system is configured to remove, by one or more processors, the first portion of the one or more pieces of personal data that are not associated with the one or more privacy campaigns of the particular entity from the one or more data assets.

Data Testing to Confirm Deletion under a Right to Erasure

In particular embodiments, a Personal Data Deletion System is configured to: (1) at least partially automatically identify and delete personal data that an entity is required to erase under one or more of the conditions discussed above; and (2) perform one or more data tests after the deletion to confirm that the system has, in fact, deleted any personal data associated with the data subject.

Various processes performed by the Personal Data Deletion System may be implemented by a Personal Data Deletion and Testing Module 5100. Referring to FIG. 51, in particular embodiments, the system, when executing the Personal Data Deletion and Testing Module 5100, is configured to: (1) receive an indication that the entity has completed an erasure of one or more pieces of personal data associated with the data subject under a right of erasure; (2) initiate a test interaction between the data subject and the entity, the test interaction requiring a response from the entity to the data subject; (3) determine whether one or more system associated with the entity have initiated a test interaction response to the data subject based at least in part on the test interaction; (4) in response to determining that the one or more systems associated with the entity have initiated the test interaction response, (a) determine that the entity has not completed the erasure of the one or more pieces of personal data associated with the data subject and (b) automatically take one or more actions with regard to the personal data associated with the data subject.

When executing the Personal Data Deletion and Testing Module 5100, the system begins, at Step S110, by receiving an indication that the entity has completed an erasure of one or more pieces of personal data associated with the data subject under a right of erasure. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more computers systems may be configured to store (e.g., in memory) an indication that the data subject's request to delete any of their personal data stored by the one or more computers systems has been processed. Under various legal and industry policies/standards, the organization may have a certain period of time (e.g., a number of days) in order to comply with the one or more requirements related to the deletion or removal of personal data in response to receiving a request from the data subject or in response to identifying one or more of the conditions requiring deletion discussed above. In response to the receiving an indication that the deletion request for the data subject's personal data has been processed or the certain period of time (described above) has passed, the system may be configured to perform a data test to confirm the deletion of the data subject's personal data.

Continuing to Step S120, in response to receiving the indication that the entity has completed the erasure, the system is configured to initiate a test interaction between the data subject and the entity, the test interaction requiring a response from the entity to the data subject. In particular embodiments, when performing the data test, the system may be configured to provide an interaction request to the entity on behalf of the data subject. In particular embodiments, the interaction request may include, for example, a request for one or more pieces of data associated with the data subject (e.g., account information, etc.). In various embodiments, the interaction request is a request to contact the data subject (e.g., for any suitable reason). The system may, for example, be configured to substantially automatically complete a contact-request form (e.g., a webform made available by the entity) on behalf of the data subject. In various embodiments, when automatically completing the form on behalf of the data subject, the system may be configured to only provide identifying data, but not to provide any contact data. In response to submitting the interaction request (e.g., submitting the webform), the system may be configured to determine whether the one or more computers systems have generated and/or transmitted a response to the data subject. The system may be configured to determine whether the one or more computers systems have generated and/or transmitted the response to the data subject by, for example, analyzing one or more computer systems associated with the entity to determine whether the one or more computer systems have generated a communication to the data subject (e.g., automatically) for transmission to an e-mail address or other contact method associated with the data subject, generated an action-item for an individual to contact the data subject at a particular contact number, etc.

To perform the data test, for example, the system may be configured to: (1) access (e.g., manually or automatically) a form for the entity (e.g., a web-based “Contact Us” form); (2) input a unique identifier associated with the data subject (e.g., a full name or customer ID number) without providing contact information for the data subject (e.g., mailing address, phone number, email address, etc.); and (3) input a request, within the form, for the entity to contact the data subject to provide information associated with the data subject (e.g., the data subject's account balance with the entity). In response to submitting the form to the entity, the system may be configured to determine whether the data subject is contacted (e.g., via a phone call or email) by the one or more computers systems (e.g., automatically). In some implementations, completing the contact-request form may include providing one or more pieces of identifying data associated with the data subject, the one or more pieces of identifying data comprising data other than contact data. In response to determining that the data subject has been contacted following submission of the form, the system may determine that the one or more computers systems have not fully deleted the data subject's personal data (e.g., because the one or more computers systems must still be storing contact information for the data subject in at least one location).

In particular embodiments, the system is configured to generate one or more test profiles for one or more test data subjects. For each of the one or more test data subjects, the system may be configured to generate and store test profile data such as, for example: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable test data. The system may then be configured to at least initially consent to processing or collection of personal data for the one or more test data subjects by the entity. The system may then request deletion of data of any personal data associated with a particular test data subject. In response to requesting the deletion of data for the particular test data subject, the system may then take one or more actions using the test profile data associated with the particular test data subjects in order to confirm that the one or more computers systems have, in fact, deleted the test data subject's personal data (e.g., any suitable action described herein). The system may, for example, be configured to: (1) initiate a contact request on behalf of the test data subject; (2) attempt to login to one or more user accounts that the system had created for the particular test data subject; and/or (3) take any other action, the effect of which could indicate a lack of complete deletion of the test data subject's personal data.

Next, at Step S130, in response to initiating the test interaction, the system is configured to determine whether one or more system associated with the entity have initiated a test interaction response to the data subject based at least in part on the test interaction. In response to determining that the entity has generated a response to the test interaction, the system may be configured to determine that the entity has not complied with the data subject's request (e.g., deletion of their personal data from the one or more computers systems). For example, if the test interaction requests for the entity to locate and provide any personal data the system has stored related to the data subject, then by the system providing a response that includes one or more pieces of personal data related to the data subject, the system may determine that the one or more computers systems have not complied with the request. As described above, the request may be an erasure of one or more pieces of personal data associated with the data subject under a right of erasure. In some implementations, the test interaction response may be any response that includes any one of the one or more pieces of personal data the system indicated was erased under the right of erasure. In some implementations, the test interaction response may not include response that indicates that the one or more pieces of personal data the system indicated was erased under the right of erasure was not found or accessed by the system.

At Step S140, in response to determining that the one or more systems associated with the entity have initiated the test interaction response the system is configured to (a) determine that the one or more computers systems have not completed the erasure of the one or more pieces of personal data associated with the data subject, and (b) automatically take one or more actions with regard to the personal data associated with the data subject. In response to determining that the one or more computers systems have not fully deleted a data subject's (e.g., or test data subject's) personal data, the system may then be configured, in particular embodiments, to: (1) flag the data subject's personal data for follow up by one or more privacy officers to investigate the lack of deletion; (2) perform one or more scans of one or more computing systems associated with the entity to identify any residual personal data that may be associated with the data subject; (3) generate a report indicating the lack of complete deletion; and/or (4) take any other suitable action to flag the data subject, personal data, initial request to be forgotten, etc. for follow up.

In various embodiments, the one or more actions may include: (1) identifying the one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity; (2) flagging the one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity; and (3) providing the flagged one or more pieces of personal data associated with the data subject that remain stored in the one or more computer systems of the entity to an individual associated with the entity.

In various embodiments, the system may monitor compliance by a particular entity with a data subject's request to delete the data subject's personal data from the one or more computers systems associated with a particular entity. The system may, for example, be configured to test to ensure the data has been deleted by: (1) submitting a unique token of data through a webform to a system (e.g., mark to); (2) in response to passage of an expected data retention time, test the system by calling into the system after the passage of the data retention time to search for the unique token. In response to finding the unique token, the system may be configured to determine that the data has not been properly deleted.

The system may provide a communication to the entity that includes a unique identifier associated with the data subject, is performed without using a personal communication data platform, prompts the entity to provide a response by contacting the data subject via a personal communication data platform. In response to providing the communication to the entity, the system may determine whether the data subject has received a response via the personal communication data platform. The system may, in response to determining that the data subject has received the response via the personal communication data platform, determine that the one or more computers systems have not complied with the data subject's request for deletion of their personal data. In response, the system may generate an indication that the one or more computers systems have not complied with the data subject's request for deletion of their personal data by the entity, and digitally store the indication that the one or more computers systems have not complied with the data subject's request for deletion of their personal data in computer memory.

Automatic Preparation for Remediation

In particular embodiments, a Risk Remediation System is configured to substantially automatically determine whether to take one or more actions in response to one or more identified risk triggers. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime). In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger.

Various processes performed by the Risk Remediation System may be implemented by a Data Risk Remediation Module 5200. Referring to FIG. 52, in particular embodiments, the system, when executing the Data Risk Remediation Module 5200, is configured to access risk remediation data for an entity that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers, receive an indication of an update to the one or more data assets, identify one or more updated risk triggers for an entity based at least in part on the update to the one or more data assets, determine, by using one or more data models associated with the risk remediation data, one or more updated actions to remediate the one or more updated risk triggers, analyze the one or more updated risk triggers to determine a relevance of the risk posed to the entity by the one or more updated risk triggers, and update the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers.

When executing the Data Risk Remediation Module 5200, the system begins, at Step S210, by accessing risk remediation data for an entity that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers. The particular entity may include, for example, a particular organization, company, sub-organization, etc. The one or more data assets may include personal data for clients or customers. In embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some implementations, the system may include risk remediation data associated with one or more data assets. The risk remediation data may be default or pre-configured risk remediation data that identifies one or more actions to remediate a risk in response to identifying one or more data assets of the entity potentially affected by one or more risk triggers. In some implementations, the system may have previously updated and/or continuously update the risk remediation data. The risk remediation data may be updated and/or based on aggregate risk remediation data for a plurality of identified risk triggers from one or more organizations, which may include the entity.

The system may analyze the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers. The remediation outcome is an indication of how well the entity response addressed the identified risk trigger. For example, the remediation outcome can be a numerical (e.g., 1 to 10), an indication of the risk trigger after the entity response was performed (e.g., “high,” “medium,” or “low”). In response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers, generating the data model of the one or more data models.

One or more data models for the system may be generated to indicate a recommended entity response based on each identified risk trigger. The one or more risk remediation models base be generated in response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers. Additionally, the risk remediation data for the entity may include the one or more risk remediation data models with an associated one or more data assets of the entity.

Continuing to Step S220, the system is configured to receive an indication of an update to the one or more data assets. In particular embodiments, the system may indicate that a modification has been performed to the one or more data assets. In various embodiments, when a privacy campaign, processing activity, etc. of the particular organization is modified (e.g., add, remove, or update particular information), then the system may the risk remediation data for use in facilitating an automatic assessment of and/or response to future identified risk triggers. The modification may be an addition (e.g., additional data stored to the one or more data assets), a deletion (e.g., removing data stored to the one or more data assets), or a change (e.g., editing particular data or rearranging a configuration of the data associated with the one or more data assets. At Step S230, the system is configured to identify one or more updated risk triggers for an entity based at least in part on the update to the one or more data assets. The updated risk triggers may be anything that exposes the one or more data assets of the entity to, for example, a data breach or a loss of data, among others. For example, an identified risk trigger may be that a data asset for an organization is hosted in only one particular location thereby increasing the scope of risk if the location were infiltrated (e.g., via cybercrime).

At Step S240, the system is configured to determine, by using one or more data models associated with the risk remediation data, one or more updated actions to remediate the one or more updated risk triggers. As previously described above, the one or more data models for the system may be generated to indicate a recommended entity response based on each identified risk trigger. The one or more risk remediation models base be generated in response to analyzing the aggregate risk remediation data to determine a remediation outcome for each of the plurality of identified risk triggers and an associated entity response to the particular identified risk trigger of the plurality of identified risk triggers.

At Step S250, the system is configured to analyze the one or more updated risk triggers to determine a relevance of the risk posed to the entity by the one or more updated risk triggers. In particular embodiments, the system is configured to substantially automatically perform one or more steps related to the analysis of and response to the one or more potential risk triggers discussed above. For example, the system may substantially automatically determine a relevance of a risk posed by (e.g., a risk level) the one or more potential risk triggers based at least in part on one or more previously-determined responses to similar risk triggers. This may include, for example, one or more previously determined responses for the particular entity that has identified the current risk trigger, one or more similarly situated entities, or any other suitable entity or potential trigger. In some embodiments, the system is configured to determine, based at least in part on the one or more data assets and the relevance of the risk, whether to take one or more updated actions in response to the one or more updated risk triggers, and take the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers.

Additionally, in some implementations, the system may calculate a risk level based at least in part on the one or more updated risk triggers. The risk level may be compared to a threshold risk level for the entity. The threshold risk level may be pre-determined, or the entity may be able to adjust the threshold risk level (e.g., based on the type of data stored in the particular data asset, a number of data assets involved, etc.). In response to determining that the risk level is greater than or equal to the threshold risk level (i.e., a risk level that is defined as riskier than the threshold risk level or as risky as the threshold risk level), updating the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers. The risk level may be, for example, a numerical value (e.g., 1 to 10) or a described value (e.g., “low,” “medium,” or “high”), among others. In some implementations, calculating the risk level may be based at least in part on the one or more updated risk triggers further comprises comparing the one or more updated risk triggers to (i) one or more previously identified risk triggers, and (ii) one or more previously implemented actions to the one or more previously identified risk triggers.

At Step S260, the system continues by updating the risk remediation data to include the one or more updated actions to remediate the risk in response to identifying the one or more updated risk triggers. In various embodiments, the system may automatically (e.g., substantially automatically) update the risk remediation data.

In various embodiments, the system may identify one or more risk triggers for an entity based at least in part on the update to the first data asset of the entity, and in turn, identify a second data asset of the entity potentially affected by the one or more risk triggers based at least in part on an association of a first data asset and the second data asset. The system may then determine, by using one or more data models, one or more first updated actions to remediate the one or more updated risk triggers for the first data asset, and determine, by using one or more data models, one or more second updated actions to remediate the one or more updated risk triggers for the second data asset. In some implementations, the one or more first updated actions to remediate the one or more updated risk triggers for the first data asset may be the same as or different from one or more second updated actions to remediate the one or more updated risk triggers for the second data asset. Further, the system may generate (or update) risk remediation data of the entity to include the one or more first updated actions and the one or more second updated actions to remediate the one or more potential risk triggers.

Central Consent Repository Maintenance and Data Inventory Linking

In particular embodiments, a Central Consent System is configured to provide a third-party data repository system to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects, as described herein. Additionally, the Central Consent System is configured to interface with a centralized consent receipt management system.

Various processes performed by the Central Consent System may be implemented by a Central Consent Module 5300. Referring to FIG. 53, in particular embodiments, the system, when executing the Central Consent Module 5300, is configured to: identify a form used to collect one or more pieces of personal data, determine a data asset of a plurality of data assets of the organization where input data of the form is transmitted, add the data asset to the third-party data repository with an electronic link to the form in response to a user submitting the form, create a unique subject identifier associated with the user, transmit the unique subject identifier (i) to the third-party data repository and (ii) along with the form data provided by the user in the form, to the data asset, and digitally store the unique subject identifier (i) in the third-party data repository and (ii) along with the form data provided by the user in the form, in the data asset.

When executing the Central Consent Module 5300, the system begins, at Step S310, by identifying a form used to collect one or more pieces of personal data. The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any processor or database that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). The one or more forms may ask for personal data, and the one or more data assets may store personal data for clients or customers. In embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In particular embodiments, the system is configured to identify a form via one or more method that may include one or more website scanning tools (e.g., web crawling). The system may also receive an indication that a user is completing a form (e.g., a webform via a website) associated with the particular organization (e.g., a form to complete for a particular privacy campaign).

The form may include, for example, one or more fields that include the user's e-mail address, billing address, shipping address, and payment information for the purposes of collected payment data to complete a checkout process on an e-commerce website. The system may, for example, be configured to track data on behalf of an entity that collects and/or processes personal data related to: (1) who consented to the processing or collection of personal data (e.g., the data subject themselves or a person legally entitled to consent on their behalf such as a parent, guardian, etc.); (2) when the consent was given (e.g., a date and time); (3) what information was provided to the consenter at the time of consent (e.g., a privacy policy, what personal data would be collected following the provision of the consent, for what purpose that personal data would be collected, etc.); (4) how consent was received (e.g., one or more copies of a data capture form, webform, etc. via which consent was provided by the consenter); (5) when consent was withdrawn (e.g., a date and time of consent withdrawal if the consenter withdraws consent); and/or (6) any other suitable data related to receipt or withdrawal of consent.

Continuing to Step S320, the system is configured to determine one or more data assets of a plurality of data assets of the organization where input data of the form is transmitted. In particular embodiments, the system may determine one or more data assets of the organization that receive the form data provided by the user in the form (e.g., webform). In particular embodiments, the system is configured to identify the one or more data assets using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset (e.g., such as a primary data asset, an example of which is shown in the center of the data model in FIG. 4); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) to identify the one or more data assets associated with the particular entity that receive and/or store particular form data.

At Step S330, the system is configured to add the one or more data assets to the third-party data repository with an electronic link to the form. In particular embodiments, a third-party data repository system may electronically link the form to the one or more data assets that processor or store the form data of the form. Next, at Step S340, in response to a user submitting the form, the system is configured to create a unique subject identifier associated with the user. The system is configured to generate, for each data subject that completes the form (e.g., a webform), a unique identifier. The system may, for example: (1) receive an indication that the form has been completed with the form including a piece of personal data; (2) identify a data subject associated with the piece of personal data; (3) determine whether the central repository system is currently storing data associated with the data subject; and (4) in response to determining that one or more data assets of the plurality of data assets is not currently storing data associated with the data subject (e.g., because the data subject is a new data subject), generate the unique identifier.

In particular embodiments, the unique identifier may include any unique identifier such as, for example: (1) any of the one or more pieces of personal data collected, stored, and/or processed by the system (e.g., name, first name, last name, full name, address, phone number, e-mail address, etc.); (2) a unique string or hash comprising any suitable number of numerals, letters, or combination thereof; and/or (3) any other identifier that is sufficiently unique to distinguish between a first and second data subject for the purpose of subsequent data retrieval. In particular embodiments, the system is configured to assign a permanent identifier to each particular data subject. In other embodiments, the system is configured to assign one or more temporary unique identifiers to the same data subject.

In particular embodiments, the system is configured to: (1) receive an indication of completion of a form associated with the organization by a data subject; (2) determine, based at least in part on searching a unique subject identifier database (e.g., a third-party data repository), whether a unique subject identifier has been generated for the data subject; (3) in response to determining that a unique subject identifier has been generated for the data subject, accessing the unique subject identifier database; (4) identify the unique subject identifier of the data subject based at least in part on form data provided by the data subject in the completion of the form associated with the organization; and (5) update the unique subject identifier database to include an electronic link between the unique subject identifier of the data subject with each of (i) the form (e.g., including the form data) submitted by the data subject of each respective unique subject identifier, and (ii) one or more data assets that utilize the form data of the form received from the data subject. In this way, as an entity collects additional data for a particular unique data subject (e.g., having a unique subject identifier, hash, etc.), the third party data repository system is configured to maintain a centralized database of data collected, stored, and or processed for each unique data subject (e.g., indexed by unique subject identifier). The system may then, in response to receiving a data subject access request from a particular data subject, fulfill the request substantially automatically (e.g., by providing a copy of the personal data, deleting the personal data, indicating to the entity what personal data needs to be deleted from their system and where it is located, etc.). The system may, for example, automatically fulfill the request by: (1) identifying the unique subject identifier associated with the unique data subject making the request; and (2) retrieving any information associated with the unique data subject based on the unique subject identifier.

Continuing to Step S350, the system is configured to transmit the unique subject identifier (i) to the third-party data repository and (ii) along with the form data provided by the user in the form, to the data asset. At Step S360, the system is configured to digitally store the unique subject identifier (i) in the third-party data repository and (ii) along with the form data provided by the user in the form, in the data asset. As may understood in light of this disclosure, the system may then be configured to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects and the associated one or more data assets that process or store the form data provided by the data subject.

In particular embodiments, the system may be further configured for receiving a data subject access request from the user, accessing the third-party data repository to identify the unique subject identifier of the user, determining which one or more data assets of the plurality of data assets of the organization include the unique subject identifier, and accessing personal data (e.g., form data) of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier. In particular embodiments, the data subject access request may be a subject's rights request where the data subject may be inquiring for the organization to provide all data that the particular organization has obtained on the data subject or a data subject deletion request where the data subject is requesting for the particular organization to delete all data that the particular organization has obtained on the data subject.

In particular embodiments, when the data subject access request is a data subject deletion request, in response to accessing the personal data of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier, the system deletes the personal data of the user stored in each of the one or more data assets of the plurality of data assets of the organization that include the unique subject identifier. In some embodiments, when the data subject access request is a data subject deletion request, the system may be configured to: (1) in response to accessing the personal data of the user stored in each of the one or more data assets of the plurality of data assets, automatically determine that a first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage; (2) in response to determining that the first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage, automatically maintain storage of the first portion of personal data of the user stored in the one or more data assets; (3) in response to determining that the first portion of personal data of the user stored in the one or more data assets has one or more legal bases for continued storage, automatically maintaining storage of the first portion of personal data of the user stored in the one or more data assets; and (4) automatically facilitating deletion of a second portion of personal data of the user stored in the one or more data assets for which one or more legal bases for continued storage cannot be determined, wherein the first portion of the personal data of the user stored in the one or more data assets is different from the second portion of personal data of the user stored in the one or more data assets.

Data Transfer Risk Identification and Analysis

In particular embodiments, a Data Transfer Risk Identification System is configured to analyze one or more data systems (e.g., data assets), identify data transfers between/among those systems, apply data transfer rules to each data transfer record, perform a data transfer assessment on each data transfer record based on the data transfer rules to be applied to each data transfer record, and calculate a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record.

Various processes performed by the Data Transfer Risk Identification System may be implemented by Data Transfer Risk Identification Module 5400. Referring to FIG. 54, in particular embodiments, the system, when executing the Data Transfer Risk Identification Module 5400, is configured for: (1) creating a data transfer record for a data transfer between a first asset in a first location and a second asset in a second location; (2) accessing a set of data transfer rules that are associated with the data transfer record; (3) performing a data transfer assessment based at least in part on applying the set of data transfer rules on the data transfer record; (4) identifying one or more data transfer risks associated with the data transfer record, based at least in part on the data transfer assessment; (5) calculating a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record; and (6) digitally storing the risk score for the data transfer.

When executing the Data Transfer Risk Identification Module 5400, the system begins, at Step S410, by creating a data transfer record for a data transfer between a first asset in a first location and a second asset in a second location. The data transfer record may be created for each transfer of data between a first asset in a first location and a second asset in a second location where the transfer record may also include information regarding the type of data being transferred, a time of the data transfer, an amount of data being transferred, etc. In some embodiments, the system may access a data transfer record that may have already been created by the system.

In various embodiments, the system may be configured to determine in which of the one or more defined plurality of physical locations each particular data system is physically located. In particular embodiments, the system is configured to determine the physical location based at least in part on one or more data attributes of a particular data asset (e.g., data system) using one or more data modeling techniques (e.g., using one or more suitable data modeling techniques described herein). In some embodiments, the system may be configured to determine the physical location of each data asset based at least in part on an existing data model that includes the data asset. In still other embodiments, the system may be configured to determine the physical location based at least in part on an IP address and/or domain of the data asset (e.g., in the case of a computer server or other computing device) or any other identifying feature of a particular data asset.

In particular embodiments, the system is configured to identify one or more data elements stored by the one or more data systems that are subject to transfer (e.g., transfer to the one or more data systems such as from a source asset, transfer from the one or more data systems to a destination asset, etc.). In particular embodiments, the system is configured to identify a particular data element that is subject to such transfer (e.g., such as a particular piece of personal data or other data). In some embodiments, the system may be configured to identify any suitable data element that is subject to transfer and includes personal data.

In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein.

In some embodiments, with regard to the location of the one or more data assets, the system may define a geographic location of the one or more data assets. For example, define each of the plurality of physical locations based at least in part on one or more geographic boundaries. These one or more geographic boundaries may include, for example: (1) one or more countries; (2) one or more continents; (3) one or more jurisdictions (e.g., such as one or more legal jurisdictions); (4) one or more territories; (5) one or more counties; (6) one or more cities; (7) one or more treaty members (e.g., such as members of a trade, defense, or other treaty); and/or (8) any other suitable geographically distinct physical locations.

Continuing to Step S420, the system is configured for accessing a set of data transfer rules that are associated with the data transfer record. The system may apply data transfer rules to each data transfer record. The data transfer rules may be configurable to support different privacy frameworks (e.g., a particular data subject type is being transferred from a first asset in the European Union to a second asset outside of the European Union) and organizational frameworks (e.g., to support the different locations and types of data assets within an organization). The applied data transfer rules may be automatically configured by the system (e.g., when an update is applied to privacy rules in a country or region) or manually adjusted by the particular organization (e.g., by a privacy officer of the organization). The data transfer rules to be applied may vary based on the data being transferred.

As may be understood from this disclosure, the transfer of personal data may trigger one or more regulations that govern such transfer. In particular embodiments, personal data may include any data which relate to a living individual who can be identified: (1) from the data; or (2) from the data in combination with other information which is in the possession of, or is likely to come into the possession of a particular entity. In particular embodiments, a particular entity may collect, store, process, and/or transfer personal data for one or more customers, one or more employees, etc.

In various embodiments, the system is configured to use one or more data models of the one or more data assets (e.g., data systems) to analyze one or more data elements associated with those assets to determine whether the one or more data elements include one or more data elements that include personal data and are subject to transfer. In particular embodiments, the transfer may include, for example: (1) an internal transfer (e.g., a transfer from a first data asset associated with the entity to a second data asset associated with the entity); (2) an external transfer (e.g., a transfer from a data asset associated with the entity to a second data asset associated with a second entity); and/or (3) a collective transfer (e.g., a transfer to a data asset associated with the entity from an external data asset associated with a second entity).

The particular entity may include, for example, a particular organization, company, sub-organization, etc. In particular embodiments, the one or more data assets (e.g., data systems) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, a first data asset may include any software or device utilized by a particular entity for such data collection, processing, transfer, storage, etc. In various embodiments, the first data asset may be at least partially stored on and/or physically located in a particular location. For example, a server may be located in a particular country, jurisdiction, etc. A piece of software may be stored on one or more servers in a particular location, etc.

In particular embodiments, the system is configured to identify the one or more data systems using one or more data modeling techniques. As discussed more fully above, a data model may store the following information: (1) the entity that owns and/or uses a particular data asset (e.g., such as a primary data asset, an example of which is shown in the center of the data model in FIG. 4); (2) one or more departments within the organization that are responsible for the data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the data asset; (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to for other use, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may utilize a data model (e.g., or one or more data models) of data assets associated with a particular entity to identify the one or more data systems associated with the particular entity.

Next, at Step S430, the system is configured for performing a data transfer assessment based at least in part on applying the set of data transfer rules on the data transfer record. The data transfer assessment performed by the system may identify risks associated with the data transfer record. At Step S440, the system is configured for identifying one or more data transfer risks associated with the data transfer record, based at least in part on the data transfer assessment. The one or more data transfer risks may include, for example, a source location of the first location of the one or more first data asset of the data transfer, a destination location of the second location of the one or more second data asset of the data transfer, one or more type of data being transferred as part of the data transfer (e.g., personal data or sensitive data), a time of the data transfer (e.g., date, day of the week, time, month, etc.), an amount of data being transferred as part of the data transfer.

Continuing to Step S450, the system is configured for calculating a risk score for the data transfer based at least in part on the one or more data transfer risks associated with the data transfer record. The risk score may be calculated in a multitude of ways, and may include one or more data transfer risks such as a source location of the data transfer, a destination location of the data transfer, the type of data being transferred, a time of the data transfer, an amount of data being transferred, etc. Additionally, the system may apply weighting factors (e.g., manually or automatically determined) to the risk factors. Further, in some implementations, the system may include a threshold risk score where a data transfer may be terminated if the data transfer risk score indicates a higher risk than the threshold risk score (e.g., the data transfer risk score being higher than the threshold risk score).

In some embodiments, the system may compare the risk score for the data transfer to a threshold risk score, determine that the risk score for the data transfer is a greater risk than the threshold risk score, and in response to determining that the risk score for the data transfer is a greater risk than the threshold risk score, taking one or more action. The one or more action may include, for example, provide the data transfer record to one or more individuals (e.g., a privacy officer) for review of the data transfer record where the one or more individuals may make a decision to approve the data transfer or terminate the data transfer. In some implementations, the system may automatically terminate the data transfer.

In some implementations, the system may generate a secure link between one or more processors associated with the first asset in the first location and one or more processors associated with the second asset in the second location, and the system may further provide the data transfer via the secure link between the one or more processors associated with the first asset in the first location and the one or more processors associated with the second asset in the second location.

In various embodiments, the system may determine a weighting factor for each of the one or more data transfer risks, determine a risk rating for each of the one or more data transfer risks, and calculate the risk level for the data transfer based upon, for each respective one of the one or more data transfer risks, the risk rating for the respective data transfer risk and the weighting factor for the respective data transfer risk.

At Step S460, the system continues by digitally storing the risk score for the data transfer. In various embodiments, the system may continue by transferring the data between the first asset in the first location and the second asset in the second location. In some embodiments, the system may be configured to substantially automatically flag a particular transfer of data as problematic (e.g., because the transfer does not comply with an applicable regulation). For example, a particular regulation may require data transfers from a first asset to a second asset to be encrypted.

Exemplary System Platform According to Various Embodiments

Various embodiments of any system described herein may be implemented in the context of any suitable system (e.g., a privacy compliance system). For example, any system described herein may be implemented to analyze a particular company or other organization's data assets to generate a data model for one or more processing activities, privacy campaigns, etc. undertaken by the organization. In particular embodiments, the system may implement one or more modules in order to at least partially ensure compliance with one or more regulations (e.g., legal requirements) related to the collection and/or storage of personal data. Various aspects of the system's functionality may be executed by certain system modules, including a Data Model Generation Module 300, Data Model Population Module 11000, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900. These modules are discussed in greater detail below.

Although these modules are presented as a series of steps, it should be understood in light of this disclosure that various embodiments of the Data Model Generation Module 300, Data Model Population Module 11000, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 described herein may perform the steps described below in an order other than in which they are presented. In still other embodiments, the Data Model Generation Module 300, Data Model Population Module 11000, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 may omit certain steps described below. In various other embodiments, the Data Model Generation Module 300, Data Model Population Module 11000, Data Population Questionnaire Generation Module 1200, Intelligent Identity Scanning Module 2600, and Data Subject Access Request Fulfillment Module 2900 may perform steps in addition to those described (e.g., such as one or more steps described with respect to one or more other modules, etc.).

Data Model Generation Module

In particular embodiments, a Data Model Generation Module 300 is configured to: (1) generate a data model (e.g., a data inventory) for one or more data assets utilized by a particular organization; (2) generate a respective data inventory for each of the one or more data assets; and (3) map one or more relationships between one or more aspects of the data inventory, the one or more data assets, etc. within the data model. In particular embodiments, a data asset (e.g., data system, software application, etc.) may include, for example, any entity that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, a first data asset may include any software or device (e.g., server or servers) utilized by a particular entity for such data collection, processing, transfer, storage, etc.

In particular embodiments, a particular data asset, or collection of data assets, may be utilized as part of a particular data processing activity (e.g., direct deposit generation for payroll purposes). In various embodiments, a data model generation system may, on behalf of a particular organization (e.g., entity), generate a data model that encompasses a plurality of processing activities. In other embodiments, the system may be configured to generate a discrete data model for each of a plurality of processing activities undertaken by an organization.

Turning to FIG. 55, in particular embodiments, when executing the Data Model Generation Module 300, the system begins, at Step 310, by generating a data model for one or more data assets and digitally storing the data model in computer memory. The system may, for example, store the data model in the One or More Databases 140 described above (or any other suitable data structure). In various embodiments, generating the data model comprises generating a data structure that comprises information regarding one or more data assets, attributes and other elements that make up the data model. As may be understood in light of this disclosure, the one or more data assets may include any data assets that may be related to one another. In particular embodiments, the one or more data assets may be related by virtue of being associated with a particular entity (e.g., organization). For example, the one or more data assets may include one or more computer servers owned, operated, or utilized by the entity that at least temporarily store data sent, received, or otherwise processed by the particular entity.

In still other embodiments, the one or more data assets may comprise one or more third party assets which may, for example, send, receive and/or process personal data on behalf of the particular entity. These one or more data assets may include, for example, one or more software applications (e.g., such as Expensify to collect expense information, QuickBooks to maintain and store salary information, etc.).

Continuing to step 320, the system is configured to identify a first data asset of the one or more data assets. In particular embodiments, the first data asset may include, for example, any entity (e.g., system) that collects, processes, contains, and/or transfers data (e.g., such as a software application, “internet of things” computerized device, database, website, data-center, server, etc.). For example, the first data asset may include any software or device utilized by a particular organization for such data collection, processing, transfer, etc. In various embodiments, the first data asset may be associated with a particular processing activity (e.g., the first data asset may make up at least a part of a data flow that relates to the collection, storage, transfer, access, use, etc. of a particular piece of data (e.g., personal data)). Information regarding the first data asset may clarify, for example, one or more relationships between and/or among one or more other data assets within a particular organization. In a particular example, the first data asset may include a software application provided by a third party (e.g., a third party vendor) with which the particular entity interfaces for the purpose of collecting, storing, or otherwise processing personal data (e.g., personal data regarding customers, employees, potential customers, etc.).

In particular embodiments, the first data asset is a storage asset that may, for example: (1) receive one or more pieces of personal data form one or more collection assets; (2) transfer one or more pieces of personal data to one or more transfer assets; and/or (3) provide access to one or more pieces of personal data to one or more authorized individuals (e.g., one or more employees, managers, or other authorized individuals within a particular entity or organization). In a particular embodiment, the first data asset is a primary data asset associated with a particular processing activity around which the system is configured to build a data model associated with the particular processing activity.

In particular embodiments, the system is configured to identify the first data asset by scanning a plurality of computer systems associated with a particular entity (e.g., owned, operated, utilized, etc. by the particular entity). In various embodiments, the system is configured to identify the first data asset from a plurality of data assets identified in response to completion, by one or more users, of one or more questionnaires.

Advancing to Step 330, the system generates a first data inventory of the first data asset. The data inventory may comprise, for example, one or more inventory attributes associated with the first data asset such as, for example: (1) one or more processing activities associated with the first data asset; (2) transfer data associated with the first data asset (e.g., how and where the data is being transferred to and/or from); (3) personal data associated with the first data asset (e.g., what type of personal data is collected and/or stored by the first data asset; how, and from where, the data is collected, etc.); (4) storage data associated with the personal data (e.g., whether the data is being stored, protected and deleted); and (5) any other suitable attribute related to the collection, use, and transfer of personal data. In other embodiments, the one or more inventory attributes may comprise one or more other pieces of information such as, for example: (1) the type of data being stored by the first data asset; (2) an amount of data stored by the first data asset; (3) whether the data is encrypted; (4) a location of the stored data (e.g., a physical location of one or more computer servers on which the data is stored); etc. In particular other embodiments, the one or more inventory attributes may comprise one or more pieces of information technology data related to the first data asset (e.g., such as one or more pieces of network and/or infrastructure information, IP address, MAC address, etc.).

In various embodiments, the system may generate the data inventory based at least in part on the type of first data asset. For example, particular types of data assets may have particular default inventory attributes. In such embodiments, the system is configured to generate the data inventory for the first data asset, which may, for example, include one or more placeholder fields to be populated by the system at a later time. In this way, the system may, for example, identify particular inventory attributes for a particular data asset for which information and/or population of data is required as the system builds the data model.

As may be understood in light of this disclosure, the system may, when generating the data inventory for the first data asset, generate one or more placeholder fields that may include, for example: (1) the organization (e.g., entity) that owns and/or uses the first data asset (a primary data asset, which is shown in the center of the data model in FIG. 56); (2) one or more departments within the organization that are responsible for the first data asset; (3) one or more software applications that collect data (e.g., personal data) for storage in and/or use by the first data asset (e.g., or one or more other suitable collection assets from which the personal data that is collected, processed, stored, etc. by the first data asset is sourced); (4) one or more particular data subjects (or categories of data subjects) that information is collected from for use by the first data asset; (5) one or more particular types of data that are collected by each of the particular applications for storage in and/or use by the first data asset; (6) one or more individuals (e.g., particular individuals or types of individuals) that are permitted to access and/or use the data stored in, or used by, the first data asset; (7) which particular types of data each of those individuals are allowed to access and use; and (8) one or more data assets (destination assets) that the data is transferred to from the first data asset, and which particular data is transferred to each of those data assets.

As may be understood in light of this disclosure, the system may be configured to generate the one or more placeholder fields based at least in part on, for example: (1) the type of the first data asset; (2) one or more third party vendors utilized by the particular organization; (3) a number of collection or storage assets typically associated with the type of the first data asset; and/or (4) any other suitable factor related to the first data asset, its one or more inventory attributes, etc. In other embodiments, the system may substantially automatically generate the one or more placeholders based at least in part on a hierarchy and/or organization of the entity for which the data model is being built. For example, a particular entity may have a marketing division, legal department, human resources department, engineering division, or other suitable combination of departments that make up an overall organization. Other particular entities may have further subdivisions within the organization. When generating the data inventory for the first data asset, the system may identify that the first data asset will have both an associated organization and subdivision within the organization to which it is assigned. In this example, the system may be configured to store an indication in computer memory that the first data asset is associated with an organization and a department within the organization.

Next, at Step 340, the system modifies the data model to include the first data inventory and electronically links the first data inventory to the first data asset within the data model. In various embodiments, modifying the data model may include configuring the data model to store the data inventory in computer memory, and to digitally associate the data inventory with the first data asset in memory.

FIGS. 4 and 5 show a data model according to a particular embodiment. As shown in these figures, the data model may store the following information for the first data asset: (1) the organization that owns and/or uses the first data asset; (2) one or more departments within the organization that are responsible for the first data asset; (3) one or more applications that collect data (e.g., personal data) for storage in and/or use by the first data asset; (4) one or more particular data subjects that information is collected from for use by the first data asset; (5) one or more collection assets from which the first asset receives data (e.g., personal data); (6) one or more particular types of data that are collected by each of the particular applications (e.g., collection assets) for storage in and/or use by the first data asset; (7) one or more individuals (e.g., particular individuals, types of individuals, or other parties) that are permitted to access and/or use the data stored in or used by the first data asset; (8) which particular types of data each of those individuals are allowed to access and use; and (9) one or more data assets (destination assets) the data is transferred to for other use, and which particular data is transferred to each of those data assets. As shown in FIGS. 6 and 7, the system may also optionally store information regarding, for example, which business processes and processing activities utilize the first data asset.

As noted above, in particular embodiments, the data model stores this information for each of a plurality of different data assets and may include one or more links between, for example, a portion of the model that provides information for a first particular data asset and a second portion of the model that provides information for a second particular data asset.

Advancing to Step 350, the system next identifies a second data asset from the one or more data assets. In various embodiments, the second data asset may include one of the one or more inventory attributes associated with the first data asset (e.g., the second data asset may include a collection asset associated with the first data asset, a destination asset or transfer asset associated with the first data asset, etc.). In various embodiments, as may be understood in light of the exemplary data models described below, a second data asset may be a primary data asset for a second processing activity, while the first data asset is the primary data asset for a first processing activity. In such embodiments, the second data asset may be a destination asset for the first data asset as part of the first processing activity. The second data asset may then be associated with one or more second destination assets to which the second data asset transfers data. In this way, particular data assets that make up the data model may define one or more connections that the data model is configured to map and store in memory.

Returning to Step 360, the system is configured to identify one or more attributes associated with the second data asset, modify the data model to include the one or more attributes, and map the one or more attributes of the second data asset within the data model. The system may, for example, generate a second data inventory for the second data asset that comprises any suitable attribute described with respect to the first data asset above. The system may then modify the data model to include the one or more attributes and store the modified data model in memory. The system may further, in various embodiments, associate the first and second data assets in memory as part of the data model. In such embodiments, the system may be configured to electronically link the first data asset with the second data asset. In various embodiments, such association may indicate a relationship between the first and second data assets in the context of the overall data model (e.g., because the first data asset may serve as a collection asset for the second data asset, etc.).

Next, at Step 370, the system may be further configured to generate a visual representation of the data model. In particular embodiments, the visual representation of the data model comprises a data map. The visual representation may, for example, include the one or more data assets, one or more connections between the one or more data assets, the one or more inventory attributes, etc.

In particular embodiments, generating the visual representation (e.g., visual data map) of a particular data model (e.g., data inventory) may include, for example, generating a visual representation that includes: (1) a visual indication of a first data asset (e.g., a storage asset), a second data asset (e.g., a collection asset), and a third data asset (e.g., a transfer asset); (2) a visual indication of a flow of data (e.g., personal data) from the second data asset to the first data asset (e.g., from the collection asset to the storage asset); (3) a visual indication of a flow of data (e.g., personal data) from the first data asset to the third data asset (e.g., from the storage asset to the transfer asset); (4) one or more visual indications of a risk level associated with the transfer of personal data; and/or (5) any other suitable information related to the one or more data assets, the transfer of data between/among the one or more data assets, access to data stored or collected by the one or more data assets, etc.

In particular embodiments, the visual indication of a particular asset may comprise a box, symbol, shape, or other suitable visual indicator. In particular embodiments, the visual indication may comprise one or more labels (e.g., a name of each particular data asset, a type of the asset, etc.). In still other embodiments, the visual indication of a flow of data may comprise one or more arrows. In particular embodiments, the visual representation of the data model may comprise a data flow, flowchart, or other suitable visual representation.

In various embodiments, the system is configured to display (e.g., to a user) the generated visual representation of the data model on a suitable display device.

Exemplary Data Models and Visual Representations of Data Models (e.g., Data Maps)

FIGS. 56-62 depict exemplary data models according to various embodiments of the system described herein. FIG. 56, for example, depicts an exemplary data model that does not include a particular processing activity (e.g., that is not associated with a particular processing activity). As may be understood from the data model shown in this figure, a particular data asset (e.g., a primary data asset) may be associated with a particular company (e.g., organization), or organization within a particular company, sub-organization of a particular organization, etc. In still other embodiments, the particular asset may be associated with one or more collection assets (e.g., one or more data subjects from whom personal data is collected for storage by the particular asset), one or more parties that have access to data stored by the particular asset, one or more transfer assets (e.g., one or more assets to which data stored by the particular asset may be transferred), etc.

As may be understood from FIG. 56, a particular data model for a particular asset may include a plurality of data elements. When generating the data model for the particular asset, a system may be configured to substantially automatically identify one or more types of data elements for inclusion in the data model, and automatically generate a data model that includes those identified data elements (e.g., even if one or more of those data elements must remain unpopulated because the system may not initially have access to a value for the particular data element). In such cases, the system may be configured to store a placeholder for a particular data element until the system is able to populate the particular data element with accurate data.

As may be further understood from FIG. 56, the data model shown in FIG. 56 may represent a portion of an overall data model. For example, in the embodiment shown in this figure, the transfer asset depicted may serve as a storage asset for another portion of the data model. In such embodiments, the transfer asset may be associated with a respective one or more of the types of data elements described above. In this way, the system may generate a data model that may build upon itself to comprise a plurality of layers as the system adds one or more new data assets, attributes, etc.

As may be further understood from FIG. 56, a particular data model may indicate one or more parties that have access to and/or use of the primary asset (e.g., storage asset). In such embodiments, the system may be configured to enable the one or more parties to access one or more pieces of data (e.g., personal data) stored by the storage asset.

As shown in FIG. 56, the data model may further comprise one or more collection assets (e.g., one or more data assets or individuals from which the storage asset receives data such as personal data). In the exemplary data model (e.g., visual data map) shown in this figure, the collection assets comprise a data subject (e.g., an individual that may provide data to the system for storage in the storage asset) and a collection asset (e.g., which may transfer one or more pieces of data that the collection asset has collected to the storage asset).

FIG. 57 depicts a portion of an exemplary data model that is populated for the primary data asset Gusto. Gusto is a software application that, in the example shown in FIG. 57, may serve as a human resources service that contains financial, expense, review, time and attendance, background, and salary information for one or more employees of a particular organization (e.g., GeneriTech). In the example of FIG. 57, the primary asset (e.g., Gusto) may be utilized by the HR (e.g., Human Resources) department of the particular organization (e.g., GeneriTech). Furthermore, the primary asset, Gusto, may collect financial information from one or more data subjects (e.g., employees of the particular organization), receive expense information transferred from Expensify (e.g., expensing software), and receive time and attendance data transferred from Kronos (e.g., timekeeping software). In the example shown in FIG. 57, access to the information collected and/or stored by Gusto may include, for example: (1) an ability to view and administer salary and background information by HR employees, and (2) an ability to view and administer employee review information by one or more service managers. In the example shown in this figure, personal and other data collected and stored by Gusto (e.g., salary information, etc.) may be transferred to a company banking system, to QuickBooks, and/or to an HR file cabinet.

As may be understood from the example shown in FIG. 57, the system may be configured to generate a data model based around Gusto that illustrates a flow of personal data utilized by Gusto. The data model in this example illustrates, for example, a source of personal data collected, stored and/or processed by Gusto, a destination of such data, an indication of who has access to such data within Gusto, and an organization and department responsible for the information collected by Gusto. In particular embodiments, the data model and accompanying visual representation (e.g., data map) generated by the system as described in any embodiment herein may be utilized in the context of compliance with one or more record keeping requirements related to the collection, storage, and processing of personal data.

FIGS. 58 and 59 depict an exemplary data model and related example that is similar, in some respects, to the data model and example of FIGS. 56 and 57. In the example shown in FIGS. 58 and 59, the exemplary data model and related example include a specific business process and processing activity that is associated with the primary asset (Gusto). In this example, the business process is compensation and the specific processing activity is direct deposit generation in Gusto. As may be understood from this figure, the collection and transfer of data related to the storage asset of Gusto is based on a need to generate direct deposits through Gusto in order to compensate employees. Gusto generates the information needed to conduct a direct deposit (e.g., financial and salary information) and then transmits this information to: (1) a company bank system for execution of the direct deposit; (2) Quickbooks for use in documenting the direct deposit payment; and (3) HR File cabinet for use in documenting the salary info and other financial information.

As may be understood in light of this disclosure, when generating such a data model, particular pieces of data (e.g., data attributes, data elements) may not be readily available to the system. In such embodiment, the system is configured to identify a particular type of data, create a placeholder for such data in memory, and seek out (e.g., scan for and populate) an appropriate piece of data to further populate the data model. For example, in particular embodiments, the system may identify Gusto as a primary asset and recognize that Gusto stores expense information. The system may then be configured to identify a source of the expense information (e.g., Expensify).

FIG. 60 depicts an exemplary screen display 800 that illustrates a visual representation (e.g., visual data map) of a data model (e.g., a data inventory). In the example shown in FIG. 8, the data map provides a visual indication of a flow of data collected from particular data subjects (e.g., employees 801). As may be understood from this figure, the data map illustrates that three separate data assets receive data (e.g., which may include personal data) directly from the employees 801. In this example, these three data assets include Kronos 803 (e.g., a human resources software application), Workday 805 (e.g., a human resources software application), and ADP 807 (e.g., a human resources software application and payment processor). As shown in FIG. 60, the transfer of data from the employees 801 to these assets is indicated by respective arrows.

As further illustrated in FIG. 60, the data map indicates a transfer of data from Workday 805 to ADP 807 as well as to a Recovery Datacenter 809 and a London HR File Center 811. As may be understood in light of this disclosure, the Recovery Datacenter 809 and London HR File Center 811 may comprise additional data assets in the context of the data model illustrated by the data map shown in FIG. 60. The Recover Datacenter 809 may include, for example, one or more computer servers (e.g., backup servers). The London HR File Center 811 may include, for example, one or more databases (e.g., such as the One or More Databases 140 shown in FIG. 1). As shown in FIG. 60, each particular data asset depicted in the data map may be shown along with a visual indication of the type of data asset. For example, Kronos 803, Workday 805, and ADP 807 are depicted adjacent a first icon type (e.g., a computer monitor), while Recover Datacenter 809 and London HR File Center 811 are depicted adjacent a second and third icon type respectively (e.g., a server cluster and a file folder). In this way, the system may be configured to visually indicate, via the data model, particular information related to the data model in a relatively minimal manner.

FIG. 61 depicts an exemplary screen display 900 that illustrates a data map of a plurality of assets 905 in tabular form (e.g., table form). As may be understood from this figure, a table that includes one or more inventory attributes of each particular asset 905 in the table may indicate, for example: (1) a managing organization 910 of each respective asset 905; (2) a hosting location 915 of each respective asset 905 (e.g., a physical storage location of each asset 905); (3) a type 920 of each respective asset 905, if known (e.g., a database, software application, server, etc.); (4) a processing activity 925 associated with each respective asset 905; and/or (5) a status 930 of each particular data asset 905. In various embodiments, the status 930 of each particular asset 905 may indicate a status of the asset 905 in the discovery process. This may include, for example: (1) a “new” status for a particular asset that has recently been discovered as an asset that processes, stores, or collects personal data on behalf of an organization (e.g., discovered via one or more suitable techniques described herein); (2) an “in discovery” status for a particular asset for which the system is populating or seeking to populate one or more inventory attributes, etc.

FIG. 62 depicts an exemplary data map that includes an asset map of a plurality of data assets 1005A-F, which may, for example, be utilized by a particular entity in the collection, storage, and/or processing of personal data. As may be understood in light of this disclosure, the plurality of data assets 1005A-F may have been discovered using any suitable technique described herein (e.g., one or more intelligent identity scanning techniques, one or more questionnaires, one or more application programming interfaces, etc.). In various embodiments, a data inventory for each of the plurality of data assets 1005A-F may define, for each of the plurality of data assets 1005A-F a respective inventory attribute related to a storage location of the data asset.

As may be understood from this figure, the system may be configured to generate a map that indicates a location of the plurality of data assets 1005A-F for a particular entity. In the embodiment shown in this figure, locations that contain a data asset are indicated by circular indicia that contain the number of assets present at that location. In the embodiment shown in this figure, the locations are broken down by country. In particular embodiments, the asset map may distinguish between internal assets (e.g., first party servers, etc.) and external/third party assets (e.g., third party owned servers or software applications that the entity utilizes for data storage, transfer, etc.).

In some embodiments, the system is configured to indicate, via the visual representation, whether one or more assets have an unknown location (e.g., because the data model described above may be incomplete with regard to the location). In such embodiments, the system may be configured to: (1) identify the asset with the unknown location; (2) use one or more data modeling techniques described herein to determine the location (e.g., such as pinging the asset, generating one or more questionnaires for completion by a suitable individual, etc.); and (3) update a data model associated with the asset to include the location.

Data Model Population Module

In particular embodiments, a Data Model Population Module 11000 is configured to: (1) determine one or more unpopulated inventory attributes in a data model; (2) determine one or more attribute values for the one or more unpopulated inventory attributes; and (3) modify the data model to include the one or more attribute values.

Turning to FIG. 63, in particular embodiments, when executing the Data Model Population Module 11000, the system begins, at Step 11100, by analyzing one or more data inventories for each of the one or more data assets in the data model. The system may, for example, identify one or more particular data elements (e.g., inventory attributes) that make up the one or more data inventories. The system may, in various embodiments, scan one or more data structures associated with the data model to identify the one or more data inventories. In various embodiments, the system is configured to build an inventory of existing (e.g., known) data assets and identify inventory attributes for each of the known data assets.

Continuing to Step 11200, the system is configured to determine, for each of the one or more data inventories, one or more populated inventory attributes and one or more unpopulated inventory attributes (e.g., and/or one or more unpopulated data assets within the data model). As a particular example related to an unpopulated data asset, when generating and populating a data model, the system may determine that, for a particular asset, there is a destination asset. In various embodiments, the destination asset may be known (e.g., and already stored by the system as part of the data model). In other embodiments, the destination asset may be unknown (e.g., a data element that comprises the destination asset may comprise a placeholder or other indication in memory for the system to populate the unpopulated inventory attribute (e.g., data element).

As another particular example, a particular storage asset may be associated with a plurality of inventory assets (e.g., stored in a data inventory associated with the storage asset). In this example, the plurality of inventory assets may include an unpopulated inventory attribute related to a type of personal data stored in the storage asset. The system may, for example, determine that the type of personal data is an unpopulated inventory asset for the particular storage asset.

Returning to Step 11300, the system is configured to determine, for each of the one or more unpopulated inventory attributes, one or more attribute values. In particular embodiments, the system may determine the one or more attribute values using any suitable technique (e.g., any suitable technique for populating the data model). In particular embodiments, the one or more techniques for populating the data model may include, for example: (1) obtaining data for the data model by using one or more questionnaires associated with a particular privacy campaign, processing activity, etc.; (2) using one or more intelligent identity scanning techniques discussed herein to identify personal data stored by the system and then map such data to a suitable data model; (3) using one or more application programming interfaces (API) to obtain data for the data model from another software application; and/or (4) using any other suitable technique. Exemplary techniques for determining the one or more attribute values are described more fully below. In other embodiments, the system may be configured to use such techniques or other suitable techniques to populate one or more unpopulated data assets within the data model.

Next, at Step 11400, the system modifies the data model to include the one or more attribute values for each of the one or more unpopulated inventory attributes. The system may, for example, store the one or more attributes values in computer memory, associate the one or more attribute values with the one or more unpopulated inventory attributes, etc. In still other embodiments, the system may modify the data model to include the one or more data assets identified as filling one or more vacancies left within the data model by the unpopulated one or more data assets.

Continuing to Step 11500, the system is configured to store the modified data model in memory. In various embodiments, the system is configured to store the modified data model in the One or More Databases 140, or in any other suitable location. In particular embodiments, the system is configured to store the data model for later use by the system in the processing of one or more data subject access requests. In other embodiments, the system is configured to store the data model for use in one or more privacy impact assessments performed by the system.

Data Model Population Questionnaire Generation Module

In particular embodiments, a Data Population Questionnaire Generation Module 1200 is configured to generate a questionnaire (e.g., one or more questionnaires) comprising one or more questions associated with one or more particular unpopulated data attributes, and populate the unpopulated data attributes based at least in part on one or more responses to the questionnaire. In other embodiments, the system may be configured to populate the unpopulated data attributes based on one or more responses to existing questionnaires.

In various embodiments, the one or more questionnaires may comprise one or more processing activity questionnaires (e.g., privacy impact assessments, data privacy impact assessments, etc.) configured to elicit one or more pieces of data related to one or more undertakings by an organization related to the collection, storage, and/or processing of personal data (e.g., processing activities). In particular embodiments, the system is configured to generate the questionnaire (e.g., a questionnaire template) based at least in part on one or more processing activity attributes, data asset attributes (e.g., inventory attributes), or other suitable attributes discussed herein.

Turning to FIG. 64, in particular embodiments, when executing the Data Population Questionnaire Generation Module 1200, the system begins, at Step 1210, by identifying one or more unpopulated data attributes from a data model. The system may, for example, identify the one or more unpopulated data attributes using any suitable technique described above. In particular embodiments, the one or more unpopulated data attributes may relate to, for example, one or more processing activity or asset attributes such as: (1) one or more processing activities associated with a particular data asset; (2) transfer data associated with the particular data asset (e.g., how and where the data stored and/or collected by the particular data asset is being transferred to and/or from); (3) personal data associated with the particular data assets asset (e.g., what type of personal data is collected and/or stored by the particular data asset; how, and from where, the data is collected, etc.); (4) storage data associated with the personal data (e.g., whether the data is being stored, protected and deleted); and (5) any other suitable attribute related to the collection, use, and transfer of personal data by one or more data assets or via one or more processing activities. In other embodiments, the one or more unpopulated inventory attributes may comprise one or more other pieces of information such as, for example: (1) the type of data being stored by the particular data asset; (2) an amount of data stored by the particular data asset; (3) whether the data is encrypted by the particular data asset; (4) a location of the stored data (e.g., a physical location of one or more computer servers on which the data is stored by the particular data asset); etc.

Continuing to Step 1220, the system generates a questionnaire (e.g., a questionnaire template) comprising one or more questions associated with one or more particular unpopulated data attributes. As may be understood in light of the above, the one or more particulate unpopulated data attributes may relate to, for example, a particular processing activity or a particular data asset (e.g., a particular data asset utilized as part of a particular processing activity). In various embodiments, the one or more questionnaires comprise one or more questions associated with the unpopulated data attribute. For example, if the data model includes an unpopulated data attribute related to a location of a server on which a particular asset stores personal data, the system may generate a questionnaire associated with a processing activity that utilizes the asset (e.g., or a questionnaire associated with the asset). The system may generate the questionnaire to include one or more questions regarding the location of the server.

Returning to Step 1230, the system maps one or more responses to the one or more questions to the associated one or more particular unpopulated data attributes. The system may, for example, when generating the questionnaire, associate a particular question with a particular unpopulated data attribute in computer memory. In various embodiments, the questionnaire may comprise a plurality of question/answer pairings, where the answer in the question/answer pairings maps to a particular inventory attribute for a particular data asset or processing activity.

In this way, the system may, upon receiving a response to the particular question, substantially automatically populate the particular unpopulated data attribute. Accordingly, at Step 1240, the system modifies the data model to populate the one or more responses as one or more data elements for the one or more particular unpopulated data attributes. In particular embodiments, the system is configured to modify the data model such that the one or more responses are stored in association with the particular data element (e.g., unpopulated data attribute) to which the system mapped it at Step 1230. In various embodiments, the system is configured to store the modified data model in the One or More Databases 140, or in any other suitable location. In particular embodiments, the system is configured to store the data model for later use by the system in the processing of one or more data subject access requests. In other embodiments, the system is configured to store the data model for use in one or more privacy impact assessments performed by the system.

Continuing to optional Step 1250, the system may be configured to modify the questionnaire based at least in part on the one or more responses. The system may, for example, substantially dynamically add and/or remove one or more questions to/from the questionnaire based at least in part on the one or more responses (e.g., one or more response received by a user completing the questionnaire). For example, the system may, in response to the user providing a particular inventory attribute or new asset, generates additional questions that relate to that particular inventory attribute or asset. The system may, as the system adds additional questions, substantially automatically map one or more responses to one or more other inventory attributes or assets. For example, in response to the user indicating that personal data for a particular asset is stored in a particular location, the system may substantially automatically generate one or more additional questions related to, for example, an encryption level of the storage, who has access to the storage location, etc.

In still other embodiments, the system may modify the data model to include one or more additional assets, data attributes, inventory attributes, etc. in response to one or more questionnaire responses. For example, the system may modify a data inventory for a particular asset to include a storage encryption data element (which specifies whether the particular asset stores particular data in an encrypted format) in response to receiving such data from a questionnaire. Modification of a questionnaire is discussed more fully below with respect to FIG. 65.

Data Model Population Via Questionnaire Process Flow

FIG. 65 depicts an exemplary process flow 1300 for populating a data model (e.g., modifying a data model to include a newly discovered data asset, populating one or more inventory attributes for a particular processing activity or data asset, etc.). In particular, FIG. 65 depicts one or more exemplary data relationships between one or more particular data attributes (e.g., processing activity attributes and/or asset attributes), a questionnaire template (e.g., a processing activity template and/or a data asset template), a completed questionnaire (e.g., a processing activity assessment and/or a data asset assessment), and a data inventory (e.g., a processing activity inventory and/or an asset inventory). As may be understood from this figure the system is configured to: (1) identify new data assets; (2) generate an asset inventory for identified new data assets; and (3) populate the generated asset inventories. Systems and methods for populating the generated inventories are described more fully below.

As may be understood from FIG. 65, a system may be configured to map particular processing activity attributes 1320A to each of: (1) a processing activity template 1330A; and (2) a processing activity data inventory 1310A. As may be understood in light of this disclosure, the processing activity template 1330A may comprise a plurality of questions (e.g., as part of a questionnaire), which may, for example, be configured to elicit discovery of one or more new data assets. The plurality of questions may each correspond to one or more fields in the processing activity inventory 1310A, which may, for example, define one or more inventory attributes of the processing activity.

In particular embodiments, the system is configured to provide a processing activity assessment 1340A to one or more individuals for completion. As may be understood from FIG. 65, the system is configured to launch the processing activity assessment 1340A from the processing activity inventory 1310A and further configured to create the processing activity assessment 1340A from the processing activity template 1330. The processing activity assessment 1340A may comprise, for example, one or more questions related to the processing activity. The system may, in various embodiments, be configured to map one or more responses provided in the processing activity assessment 1340A to one or more corresponding fields in the processing activity inventory 1310A. The system may then be configured to modify the processing activity inventory 1310A to include the one or more responses, and store the modified inventory in computer memory. In various embodiments, the system may be configured to approve a processing activity assessment 1340A (e.g., receive approval of the assessment) prior to feeding the processing activity inventory attribute values into one or more fields and/or cells of the inventory.

As may be further understood from FIG. 65, in response to creating a new asset record (e.g., which the system may create, for example, in response to a new asset discovery via the processing activity assessment 1340A described immediately above, or in any other suitable manner), the system may generate an asset inventory 1310B (e.g., a data asset inventory) that defines a plurality of inventory attributes for the new asset (e.g., new data asset).

As may be understood from FIG. 65, a system may be configured to map particular asset attributes 1320B to each of: (1) an asset template 1330BA; and (2) an asset inventory 1310A. As may be understood in light of this disclosure, the asset template 1330B may comprise a plurality of questions (e.g., as part of a questionnaire), which may, for example, be configured to elicit discovery of one or more processing activities associated with the asset and/or one or more inventory attributes of the asset. The plurality of questions may each correspond to one or more fields in the asset inventory 1310B, which may, for example, define one or more inventory attributes of the asset.

In particular embodiments, the system is configured to provide an asset assessment 1340B to one or more individuals for completion. As may be understood from FIG. 65, the system is configured to launch the asset assessment 1340B from the asset inventory 1310B and further configured to create the asset assessment 1340B from the asset template 1330B. The asset assessment 1340B may comprise, for example, one or more questions related to the data asset. The system may, in various embodiments, be configured to map one or more responses provided in the asset assessment 1340B to one or more corresponding fields in the asset inventory 1310B. The system may then be configured to modify the asset inventory 1310B (e.g., and/or a related processing activity inventory 1310A) to include the one or more responses, and store the modified inventory in computer memory. In various embodiments, the system may be configured to approve an asset assessment 1340B (e.g., receive approval of the assessment) prior to feeding the asset inventory attribute values into one or more fields and/or cells of the inventory.

FIG. 65 further includes a detail view 1350 of a relationship between particular data attributes 1320C with an exemplary data inventory 1310C and a questionnaire template 1330C. As may be understood from this detail view 1350, a particular attribute name may map to a particular question title in a template 1330C as well as to a field name in an exemplary data inventory 1310C. In this way, the system may be configured to populate (e.g., automatically populate) a field name for a particular inventory 1310C in response to a user providing a question title as part of a questionnaire template 1330C. Similarly, a particular attribute description may map to a particular question description in a template 1330C as well as to a tooltip on a fieldname in an exemplary data inventory 1310C. In this way, the system may be configured to provide the tooltip for a particular inventory 1310C that includes the question description provided by a user as part of a questionnaire template 1330C.

As may be further understood from the detail view 1350 of FIG. 65, a particular response type may map to a particular question type in a template 1330C as well as to a field type in an exemplary data inventory 1310C. A particular question type may include, for example, a multiple choice question (e.g., A, B, C, etc.), a freeform response, an integer value, a drop down selection, etc. A particular field type may include, for example, a memo field type, a numeric field type, an integer field type, a logical field type, or any other suitable field type. A particular data attribute may require a response type of, for example: (1) a name of an organization responsible for a data asset (e.g., a free form response); (2) a number of days that data is stored by the data asset (e.g., an integer value); and/or (3) any other suitable response type.

In still other embodiments, the system may be configured to map a one or more attribute values to one or more answer choices in a template 1330C as well as to one or more lists and/or responses in a data inventory 1310C. The system may then be configured to populate a field in the data inventory 1310C with the one or more answer choices provided in a response to a question template 1330C with one or more attribute values.

Intelligent Identity Scanning Module

Turning to FIG. 66, in particular embodiments, the Intelligent Identity Scanning Module 2600 is configured to scan one or more data sources to identify personal data stored on one or more network devices for a particular organization, analyze the identified personal data, and classify the personal data (e.g., in a data model) based at least in part on a confidence score derived using one or more machine learning techniques. The confidence score may be and/or comprise, for example, an indication of the probability that the personal data is actually associated with a particular data subject (e.g., that there is at least an 80% confidence level that a particular phone number is associated with a particular individual.)

When executing the Intelligent Identity Scanning Module 2600, the system begins, at Step 2610, by connecting to one or more databases or other data structures, and scanning the one or more databases to generate a catalog of one or more individuals and one or more pieces of personal information associated with the one or more individuals. The system may, for example, be configured to connect to one or more databases associated with a particular organization (e.g., one or more databases that may serve as a storage location for any personal or other data collected, processed, etc. by the particular organization, for example, as part of a suitable processing activity. As may be understood in light of this disclosure, a particular organization may use a plurality of one or more databases (e.g., the One or More Databases 140 shown in FIG. 1), a plurality of servers (e.g., the One or More Third Party Servers 160 shown in FIG. 1), or any other suitable data storage location in order to store personal data and other data collected as part of any suitable privacy campaign, privacy impact assessment, processing activity, etc.

In particular embodiments, the system is configured to scan the one or more databases by searching for particular data fields comprising one or more pieces of information that may include personal data. The system may, for example, be configured to scan and identify one of more pieces of personal data such as: (1) name; (2) address; (3) telephone number; (4) e-mail address; (5) social security number; (6) information associated with one or more credit accounts (e.g., credit card numbers); (7) banking information; (8) location data; (9) internet search history; (10) non-credit account data; and/or (11) any other suitable personal information discussed herein. In particular embodiments, the system is configured to scan for a particular type of personal data (e.g., or one or more particular types of personal data).

The system may, in various embodiments, be further configured to generate a catalog of one or more individuals that also includes one or more pieces of personal information (e.g., personal data) identified for the individuals during the scan. The system may, for example, in response to discovering one or more pieces of personal data in a particular storage location, identify one or more associations between the discovered pieces of personal data. For example, a particular database may store a plurality of individuals' names in association with their respective telephone numbers. One or more other databases may include any other suitable information.

The system may, for example, generate the catalog to include any information associated with the one or more individuals identified in the scan. The system may, for example, maintain the catalog in any suitable format (e.g., a data table, etc.).

Continuing to Step 2620, the system is configured to scan one or more structured and/or unstructured data repositories based at least in part on the generated catalog to identify one or more attributes of data associated with the one or more individuals. The system may, for example, be configured to utilize information discovered during the initial scan at Step 2610 to identify the one or more attributes of data associated with the one or more individuals.

For example, the catalog generated at Step 2610 may include a name, address, and phone number for a particular individual. The system may be configured, at Step 2620, to scan the one or more structured and/or unstructured data repositories to identify one or more attributes that are associated with one or more of the particular individual's name, address and/or phone number. For example, a particular data repository may store banking information (e.g., a bank account number and routing number for the bank) in association with the particular individual's address. In various embodiments, the system may be configured to identify the banking information as an attribute of data associated with the particular individual. In this way, the system may be configured to identify particular data attributes (e.g., one or more pieces of personal data) stored for a particular individual by identifying the particular data attributes using information other than the individual's name.

Returning to Step 2630, the system is configured to analyze and correlate the one or more attributes and metadata for the scanned one or more structured and/or unstructured data repositories. In particular embodiments, the system is configured to correlate the one or more attributes with metadata for the associated data repositories from which the system identified the one or more attributes. In this way, the system may be configured to store data regarding particular data repositories that store particular data attributes.

In particular embodiments, the system may be configured to cross-reference the data repositories that are discovered to store one or more attributes of personal data associated with the one or more individuals with a database of known data assets. In particular embodiments, the system is configured to analyze the data repositories to determine whether each data repository is part of an existing data model of data assets that collect, store, and/or process personal data. In response to determining that a particular data repository is not associated with an existing data model, the system may be configured to identify the data repository as a new data asset (e.g., via asset discovery), and take one or more actions (e.g., such as any suitable actions described herein) to generate and populate a data model of the newly discovered data asset. This may include, for example: (1) generating a data inventory for the new data asset; (2) populating the data inventory with any known attributes associated with the new data asset; (3) identifying one or more unpopulated (e.g., unknown) attributes of the data asset; and (4) taking any suitable action described herein to populate the unpopulated data attributes.

In particular embodiments, the system my, for example: (1) identify a source of the personal data stored in the data repository that led to the new asset discovery; (2) identify one or more relationships between the newly discovered asset and one or more known assets; and/or (3) etc.

Continuing to Step 2640, the system is configured to use one or more machine learning techniques to categorize one or more data elements from the generated catalog, analyze a flow of the data among the one or more data repositories, and/or classify the one or more data elements based on a confidence score as discussed below.

Continuing to Step 2650, the system, in various embodiments, is configured to receive input from a user confirming or denying a categorization of the one or more data elements, and, in response, modify the confidence score. In various embodiments, the system is configured to iteratively repeat Steps 2640 and 2650. In this way, the system is configured to modify the confidence score in response to a user confirming or denying the accuracy of a categorization of the one or more data elements. For example, in particular embodiments, the system is configured to prompt a user (e.g., a system administrator, privacy officer, etc.) to confirm that a particular data element is, in fact, associated with a particular individual from the catalog. The system may, in various embodiments, be configured to prompt a user to confirm that a data element or attribute discovered during one or more of the scans above were properly categorized at Step 2640.

In particular embodiments, the system is configured to modify the confidence score based at least in part on receiving one or more confirmations that one or more particular data elements or attributes discovered in a particular location during a scan are associated with particular individuals from the catalog. As may be understood in light of this disclosure, the system may be configured to increase the confidence score in response to receiving confirmation that particular types of data elements or attributes discovered in a particular storage location are typically confirmed as being associated with particular individuals based on one or more attributes for which the system was scanning.

Exemplary Intelligent Identity Scanning Technical Platforms

FIG. 67 depicts an exemplary technical platform via which the system may perform one or more of the steps described above with respect to the Intelligent Identity Scanning Module 2600. As shown in the embodiment in this figure, an Intelligent Identity Scanning System 2600 comprises an Intelligent Identity Scanning Server 130, such as the Intelligent Identity Scanning Server 130 described above with respect to FIG. 1. The Intelligent Identity Scanning Server 130 may, for example, comprise a processing engine (e.g., one or more computer processors). In some embodiments, the Intelligent Identity Scanning Server 130 may include any suitable cloud hosted processing engine (e.g., one or more cloud-based computer servers). In particular embodiments, the Intelligent Identity Scanning Server 130 is hosted in a Microsoft Azure cloud.

In particular embodiments, the Intelligent Identity Scanning Server 130 is configured to sit outside one or more firewalls (e.g., such as the firewall 195 shown in FIG. 26). In such embodiments, the Intelligent Identity Scanning Server 130 is configured to access One or More Remote Computing Devices 150 through the Firewall 195 (e.g., one or more firewalls) via One or More Networks 115 (e.g., such as any of the One or More Networks 115 described above with respect to FIG. 1).

In particular embodiments, the One or More Remote Computing Devices 150 include one or more computing devices that make up at least a portion of one or more computer networks associated with a particular organization. In particular embodiments, the one or more computer networks associated with the particular organization comprise one or more suitable servers, one or more suitable databases, one or more privileged networks, and/or any other suitable device and/or network segment that may store and/or provide for the storage of personal data. In the embodiment shown in FIG. 27, the one or more computer networks associated with the particular organization may comprise One or More Third Party Servers 160, One or More Databases 140, etc. In particular embodiments, the One or More Remote Computing Devices 150 are configured to access one or more segments of the one or more computer networks associated with the particular organization. In some embodiments, the one or more computer networks associated with the particular organization comprise One or More Privileged Networks 165. In still other embodiments, the one or more computer networks comprise one or more network segments connected via one or more suitable routers, one or more suitable network hubs, one or more suitable network switches, etc.

As shown in FIG. 67, various components that make up one or more parts of the one or more computer networks associated with the particular organization may store personal data (e.g., such as personal data stored on the One or More Third Party Servers 160, the One or More Databases 140, etc.). In various embodiments, the system is configured to perform one or more steps related to the Intelligent Identity Scanning Server 2600 in order to identify the personal data for the purpose of generating the catalog of individuals described above (e.g., and/or identify one or more data assets within the organization's network that store personal data)

As further shown in FIG. 67, in various embodiments, the One or More Remote Computing Devices 150 may store a software application (e.g., the Intelligent Identity Scanning Module). In such embodiments, the system may be configured to provide the software application for installation on the One or More Remote Computing Devices 150. In particular embodiments, the software application may comprise one or more virtual machines. In particular embodiments, the one or more virtual machines may be configured to perform one or more of the steps described above with respect to the Intelligent Identity Scanning Module 2600 (e.g., perform the one or more steps locally on the One or More Remote Computing Devices 150).

In various embodiments, the one or more virtual machines may have the following specifications: (1) any suitable number of cores (e.g., 4, 6, 8, etc.); (2) any suitable amount of memory (e.g., 4 GB, 8 GB, 16 GB etc.); (3) any suitable operating system (e.g., CentOS 7.2); and/or (4) any other suitable specification. In particular embodiments, the one or more virtual machines may, for example, be used for one or more suitable purposes related to the Intelligent Identity Scanning System 2700. These one or more suitable purposes may include, for example, running any of the one or more modules described herein, storing hashed and/or non-hashed information (e.g., personal data, personally identifiable data, catalog of individuals, etc.), storing and running one or more searching and/or scanning engines (e.g., Elasticsearch), etc.

In various embodiments, the Intelligent Identity Scanning System 2700 may be configured to distribute one or more processes that make up part of the Intelligent Identity Scanning Process (e.g., described above with respect to the Intelligent Identity Scanning Module 2600). The one or more software applications installed on the One or more Remote Computing Devices 150 may, for example, be configured to provide access to the one or more computer networks associated with the particular organization to the Intelligent Identity Scanning Server 130. The system may then be configured to receive, from the One or more Remote Computing Devices 150 at the Intelligent Identity Scanning Server 130, via the Firewall 195 and One or More Networks 115, scanned data for analysis.

In particular embodiments, the Intelligent Identity Scanning System 2700 is configured to reduce an impact on a performance of the One or More Remote Computing Devices 150, One or More Third Party Servers 160 and other components that make up one or more segments of the one or more computer networks associated with the particular organization. For example, in particular embodiments, the Intelligent Identity Scanning System 2700 may be configured to utilize one or more suitable bandwidth throttling techniques. In other embodiments, the Intelligent Identity Scanning System 2700 is configured to limit scanning (e.g., any of the one or more scanning steps described above with respect to the Intelligent Identity Scanning Module 2600) and other processing steps (e.g., one or more steps that utilize one or more processing resources) to non-peak times (e.g., during the evening, overnight, on weekends and/or holidays, etc.). In other embodiments, the system is configured to limit performance of such processing steps to backup applications and data storage locations. The system may, for example, use one or more sampling techniques to decrease a number of records required to scan during the personal data discovery process.

FIG. 68 depicts an exemplary asset access methodology that the system may utilize in order to access one or more network devices that may store personal data (e.g., or other personally identifiable information). As may be understood from this figure, the system may be configured to access the one or more network devices using a locally deployed software application (e.g., such as the software application described immediately above). In various embodiments, the software application is configured to route identity scanning traffic through one or more gateways, configure one or more ports to accept one or more identity scanning connections, etc.

As may be understood from this figure, the system may be configured to utilize one or more credential management techniques to access one or more privileged network portions. The system may, in response to identifying particular assets or personally identifiable information via a scan, be configured to retrieve schema details such as, for example, an asset ID, Schema ID, connection string, credential reference URL, etc. In this way, the system may be configured to identify and store a location of any discovered assets or personal data during a scan.

Data Subject Access Request Fulfillment Module

Turning to FIG. 29, in particular embodiments, a Data Subject Access Request Fulfillment Module 2900 is configured to receive a data subject access request, process the request, and fulfill the request based at least in part on one or more request parameters. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and/or (3) categories of third parties to whom the data may be disclosed.

Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example: (1) a right to obtain confirmation of whether a particular organization is processing their personal data; (2) a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected); (3) a right to obtain information about one or more categories of data being processed (e.g., what type of personal data is being collected, stored, etc.); (4) a right to obtain information about one or more categories of recipients with whom their personal data may be shared (e.g., both internally within the organization or externally); (5) a right to obtain information about a time period for which their personal data will be stored (e.g., or one or more criteria used to determine that time period); (6) a right to obtain a copy of any personal data being processed (e.g., a right to receive a copy of their personal data in a commonly used, machine-readable format); (7) a right to request erasure (e.g., the right to be forgotten), rectification (e.g., correction or deletion of inaccurate data), or restriction of processing of their personal data; and (8) any other suitable rights related to the collection, storage, and/or processing of their personal data (e.g., which may be provided by law, policy, industry or organizational practice, etc.).

As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). In particular embodiments, a data subject access request fulfillment system may utilize one or more data model generation and population techniques (e.g., such as any suitable technique described herein) to create a centralized data map with which the system can identify personal data stored, collected, or processed for a particular data subject, a reason for the processing, and any other information related to the processing.

Turning to FIG. 29, when executing the Data Subject Access Request Module 2900, the system begins, at Step 2910, by receiving a data subject access request. In various embodiments, the system receives the request via a suitable web form. In certain embodiments, the request comprises a particular request to perform one or more actions with any personal data stored by a particular organization regarding the requestor. For example, in some embodiments, the request may include a request to view one or more pieces of personal data stored by the system regarding the requestor. In other embodiments, the request may include a request to delete one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request to update one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request based on any suitable right afforded to a data subject, such as those discussed above.

Continuing to Step 2920, the system is configured to process the request by identifying and retrieving one or more pieces of personal data associated with the requestor that are being processed by the system. For example, in various embodiments, the system is configured to identify any personal data stored in any database, server, or other data repository associated with a particular organization. In various embodiments, the system is configured to use one or more data models, such as those described above, to identify this personal data and suitable related information (e.g., where the personal data is stored, who has access to the personal data, etc.). In various embodiments, the system is configured to use intelligent identity scanning (e.g., as described above) to identify the requestor's personal data and related information that is to be used to fulfill the request.

In still other embodiments, the system is configured to use one or more machine learning techniques to identify such personal data. For example, the system may identify particular stored personal data based on, for example, a country in which a website that the data subject request was submitted is based, or any other suitable information.

In particular embodiments, the system is configured to scan and/or search one or more existing data models (e.g., one or more current data models) in response to receiving the request in order to identify the one or more pieces of personal data associated with the requestor. The system may, for example, identify, based on one or more data inventories (e.g., one or more inventory attributes) a plurality of storage locations that store personal data associated with the requestor. In other embodiments, the system may be configured to generate a data model or perform one or more scanning techniques in response to receiving the request (e.g., in order to automatically fulfill the request).

Returning to Step 2930, the system is configured to take one or more actions based at least in part on the request. In some embodiments, the system is configured to take one or more actions for which the request was submitted (e.g., display the personal data, delete the personal data, correct the personal data, etc.). In particular embodiments, the system is configured to take the one or more actions substantially automatically. In particular embodiments, in response a data subject submitting a request to delete their personal data from an organization's systems, the system may: (1) automatically determine where the data subject's personal data is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's personal data from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's personal data from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., and deleting a directory entry associated with the data); and/or (3) any other suitable technique for deleting the personal data. In particular embodiments, as part of this process, the system uses an appropriate data model (see discussion above) to efficiently determine where all of the data subject's personal data is stored.

Overview of Data Subject Access Requests and Data Subject Verification

Various embodiments of a Data Subject Access Request (DSAR) Processing System are configured to receive a data subject access request, process the request, and fulfill the request based at least in part on one or more request parameters. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and/or (3) categories of third parties to whom the data may be disclosed.

Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example: (1) a right to obtain confirmation of whether a particular organization is processing their personal data; (2) a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected); (3) a right to obtain information about one or more categories of data being processed (e.g., what type of personal data is being collected, stored, etc.); (4) a right to obtain information about one or more categories of recipients with whom their personal data may be shared (e.g., both internally within the organization or externally); (5) a right to obtain information about a time period for which their personal data will be stored (e.g., or one or more criteria used to determine that time period); (6) a right to obtain a copy of any personal data being processed (e.g., a right to receive a copy of their personal data in a commonly used, machine-readable format); (7) a right to request erasure (e.g., the right to be forgotten), rectification (e.g., correction or deletion of inaccurate data), or restriction of processing of their personal data; and (8) any other suitable rights related to the collection, storage, and/or processing of their personal data (e.g., which may be provided by law, policy, industry or organizational practice, etc.).

As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). In particular embodiments, a data subject access request fulfillment system may utilize one or more data model generation and population techniques (e.g., such as any suitable technique described herein) to create a centralized data map with which the system can identify personal data stored, collected, or processed for a particular data subject, a reason for the processing, and any other information related to the processing.

In various embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access data subject placing the first data subject access request (DSAR); (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically obtaining, from a particular data model, at least a portion of information requested in the first data subject access request; and (3) after obtaining the at least a portion of the requested information, displaying the obtained information to a user as part of a fulfillment of the first data subject access request. The information requested in the first data subject access request may, for example, comprise at least substantially all (e.g., most or all) of the information regarding the first data subject that is stored within the data model.

In various embodiments, the system is adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically facilitating an update of personal data that an organization associated with the first webform is processing regarding the particular data subject access requestor.

Similarly, in particular embodiments, the system may be adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically processing a request, made by the particular data subject access requestor, to opt out of having the organization use the particular data subject access requestor's personal information in one or more particular ways.

In various embodiments, the system may be configured to verify a residency of an individual submitting a DSAR or other request. The system may, for example, require a resident of a particular state (e.g., California) to provide one or more pieces of evidence to confirm their residency in order to enable the data subject to exercise particular rights related to the submission of DSAR(s). The system may, for example, be configured to prompt a data subject to provide a social security number (e.g., or other piece of identifying information) in order to confirm their identify and verify that a name matched with the identifying information matches an address in the location for which the system is verifying residency.

For example, in particular embodiments, the system may be configured to substantially automatically (e.g., automatically) authenticate and/or verify an identity (e.g., residency) of a data subject using any suitable technique. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business data subject access request); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) etc. Various exemplary techniques for authenticating a data subject are discussed more fully below.

In particular embodiments, when authenticating a data subject (e.g., verifying the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when verifying a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the data subject access request) actually exists. In various embodiments, the system is configured to interface with (e.g., transmit a search request to) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to confirm that a person with one or more characteristics provided by the data subject exists. The system may, for example, interface with such credit reporting agencies via a suitable plugin (e.g., software plugin). Additionally, there might be a verification on behalf of a trusted third-party system (e.g., the controller).

In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, IDology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. The system may be configured to interface with one or more such third-party systems to confirm that a person with one or more characteristics provided by the data subject exists.

In still other embodiments, the system may be configured to access one or more public record databases (e.g., property tax records, property ownership and transfer recordings with a state or county authority, etc.). In still other embodiments, the system may be configured to confirm a residency of an individual by: (1) accessing one or more credit records or financial accounts of the individual; and (2) identify a location of at least one financial transaction to determine that the individual resides in the particular jurisdiction/location/etc. (e.g., by confirming a grocery store purchase at a particular location). In still other embodiments, the system may confirm a pattern of financial transactions to confirm a residency of the data subject (e.g., as opposed to relying on a single transaction that may have occurred during a temporary stay in the location).

In still other embodiments, the system may access a driver database (e.g., DMV records) to determine whether the individual holds a driver's license in the jurisdiction, has a car registered in the state/location, etc. The system may further be configured to access one or more educational records for the individual to confirm enrollment (e.g., and therefore residency) in a particular school in the location/state/jurisdiction/etc.

Data Subject Verification Module and Related Methods

As discussed in more detail herein, a data subject may submit a subject access request, for example, to request a listing of any personal information that a particular organization is currently storing regarding the data subject, to request that the personal data be deleted, to opt out of allowing the organization to process the personal data, etc. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and/or (3) categories of third parties to whom the data may be disclosed. Various embodiments of a data subject access request verification system are described more fully below.

In particular embodiments, a Data Subject Verification Module 7000 is configured to receive a data subject access request, verify that the data subject is associated with the particular geographic location, process the request, and fulfill the request based at least in part on one or more request parameters. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and (3) categories of third parties to whom the data may be disclosed. In particular embodiments, when processing a data subject access request, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step).

Turning to FIG. 70, when executing the Data Subject Verification Module 3600, the system begins, at Step 7010, by receiving a data subject access request. In various embodiments, the system receives the request via a suitable web form. In certain embodiments, the request comprises a particular request to perform one or more actions with any personal data stored by a particular organization regarding the requestor. For example, in some embodiments, the request may include a request to view one or more pieces of personal data stored by the system regarding the requestor (e.g., a subject's rights request). In other embodiments, the request may include a request to delete one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request to update one or more pieces of personal data stored by the system regarding the requestor.

Continuing to Step 7020, the system is configured for determining that the data subject is associated with a particular geographic location. In some implementations, the data subject, when providing the data subject access request, may identify the particular geographic location. For example, the particular geographic location may be a country, state (or province), county, and/or city of residence of the data subject. The particular geographic location may also be a location where data is transmitted from or transmitted to.

In some implementations, the system may automatically determine a location of the data subject when providing the data subject access request. For example, the system may determine that a data subject is located in a jurisdiction, country, or other geographic location when providing the data subject access request. The system may be configured to determine the data subject's location based at least in part on, for example, a geolocation (e.g., GPS location) of a mobile computing device associated with the data subject, an IP address of one or more computing devices associated with the data subject, etc.). As may be understood in light of this disclosure, one or more different countries, jurisdictions, etc. may impose different rules, regulations, etc. related to data subject access requests, and the collection, storage, and processing of personal data. The system may, for example, require a resident of a particular state (e.g., California) to provide one or more pieces of evidence to confirm their residency in order to enable the data subject to exercise particular rights related to the submission of DSAR(s).

Next, at Step 7030, the system is configured for verifying that the data subject is associated with the particular geographic location. In various embodiments, verifying that the data subject is associated with the particular geographic location may, for example, limit a risk that a third-party or other entity may gain unlawful or unconsented access to the requestor's personal data. As described above, the particular geographic location associated with the data subject may be a location of residence (e.g., a county, state, county, city, zip code, etc.) of the data subject. In various embodiments, the system may be configured to verify the residence of data subject. One or more different privacy laws or set of privacy laws may pertain to individuals that are residents of particular geographic locations.

In various embodiments, to verify the particular geographic location associated with the data subject, the system may be configured to prompt the data subject to provide one or more additional pieces of information. The additional information called for by the prompt to the data subject may include, for example: (1) at least a portion of the data subject's social security number (e.g., last four digits); (2) an address of the data subject; (3) financial transaction information; and/or (4) any other information which may be useful for verifying the particular geographic location associated with the data subject.

In some embodiments, the system may prompt the user to provide the additional information of one or more images (e.g., using a suitable mobile computing device) of additional information, such as a location or individual identifying document (e.g., utility bill, social security card, driver's license, financial transaction data, address, property tax information, etc.). The data identifying the additional information may be provided by the data subject to the system via a secure terminal or secure link to prevent interception of the data or unwarranted access to the additional information. Additionally, the data identifying the additional information may be encrypted for the transmission of the data.

In particular embodiments, the system may be configured to interface with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when verifying the particular geographic location associated with the data subject, may begin by accessing the one or more third-party data aggregation systems. In various embodiments, the system third-party data aggregation systems may include, for example: (1) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to determine and confirm information related to a data subject (e.g., location of residence); (2) one or more other third-party systems (e.g., such as LexisNexis, IDology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals; (3) one or more public record databases (e.g., property tax records, property ownership and transfer recordings with a state or county authority, etc.).

In various embodiments, the system may compare the one or more additional pieces of information received from the data subject to corresponding data information accessed via one or more third-party data aggregation systems in order to verify that the data subject is associated with the particular geographic location. For example, the one or more additional pieces of information provided by the data subject may identify an address of the data subject (e.g., a utility bill, driver's license, IP address geo-location of the data subject's computing device that executed the data subject access request at the time of the request), etc.). The system may then access one or more third-party data aggregation systems to determine a property identification address of residence of the data subject based at least in part on accessing the one or more property identification databases (e.g., a property tax record database). Further, the system may compare the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject, and in response, the system may verify that the data subject is associated with the particular geographic location based at least in part on the comparing of the address of residence of the data subject identified in the one or more additional pieces of information to the property identification address of residence of the data subject.

In still other embodiments, the system may be configured to confirm a residency of an individual by: (1) accessing one or more credit records or financial accounts of the individual; and (2) identify a location of at least one financial transaction to determine that the individual resides in the particular jurisdiction/location/etc. (e.g., by confirming a grocery store purchase at a particular location). In still other embodiments, the system may confirm a pattern of financial transactions to confirm a residency of the data subject (e.g., as opposed to relying on a single transaction that may have occurred during a temporary stay in the location).

In still other embodiments, the system may access a driver database (e.g., DMV records) to determine whether the individual holds a driver's license in the jurisdiction, has a car registered in the state/location, etc. The system may further be configured to access one or more educational records for the individual to confirm enrollment (e.g., and therefore residency) in a particular school in the location/state/jurisdiction/etc. confirming that the data subject is associated with a particular geographic location based at least in part on the one or more additional pieces of information

In various embodiments, one or more pieces of additional information may not be required to be provided from the data subject, and the system may access one or more third-party data aggregation systems to verify that the data subject is associated with the particular geographic location. For example, at the time of issuing the data subject access request, the system may identify use geo-location processes to determine a location associated with the data subject's computing device (e.g., identifying an IP address of the computing device) that executed the data subject access request at the time of the request. The location may, for example, correspond to a residence location of the data subject (e.g., the data subject issued the data subject access request from their computing device at their residence). In response, the system may access one or more third-party aggregation system (e.g., property tax record database) to verify that the data subject is associated with the particular geographic location.

At Step 7040, the system is configured to process the request by identifying, and retrieving one or more pieces of personal data associated with the requestor that are being processed by the system. For example, in various embodiments, the system is configured to identify any personal data stored in any database, server, or other data repository associated with a particular organization. In various embodiments, the system is configured to use one or more data models, such as those described above, to identify this personal data and suitable related information (e.g., where the personal data is stored, who has access to the personal data, etc.). In various embodiments, the system is configured to use intelligent identity scanning (e.g., as described above) to identify the requestor's personal data and related information that is to be used to fulfill the request.

In still other embodiments, the system is configured to use one or more machine learning techniques to identify such personal data. For example, the system may identify particular stored personal data based on, for example, a country in which a website that the data subject request was submitted is based, or any other suitable information.

Turning to Step 7050, the system is configured to take one or more actions based at least in part on the request. In some embodiments, the system is configured to take one or more actions for which the request was submitted (e.g., display the personal data, delete the personal data, correct the personal data, etc.). In particular embodiments, the system is configured to take the one or more actions substantially automatically.

Overview of Data Subject Access Requests and Data Subject Cookie Verification

Various embodiments of a Data Subject Access Request (DSAR) Processing System are configured to receive a data subject access request, process the request, and fulfill the request based at least in part on one or more request parameters. In various embodiments, an organization, corporation, etc. may be required to provide information requested by an individual for whom the organization stores personal data within a certain time period (e.g., 30 days). As a particular example, an organization may be required to provide an individual with a listing of, for example: (1) any personal data that the organization is processing for an individual, (2) an explanation of the categories of data being processed and the purpose of such processing; and/or (3) categories of third parties to whom the data may be disclosed.

Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example: (1) a right to obtain confirmation of whether a particular organization is processing their personal data; (2) a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected); (3) a right to obtain information about one or more categories of data being processed (e.g., what type of personal data is being collected, stored, etc.); (4) a right to obtain information about one or more categories of recipients with whom their personal data may be shared (e.g., both internally within the organization or externally); (5) a right to obtain information about a time period for which their personal data will be stored (e.g., or one or more criteria used to determine that time period); (6) a right to obtain a copy of any personal data being processed (e.g., a right to receive a copy of their personal data in a commonly used, machine-readable format); (7) a right to request erasure (e.g., the right to be forgotten), rectification (e.g., correction or deletion of inaccurate data), or restriction of processing of their personal data; and (8) any other suitable rights related to the collection, storage, and/or processing of their personal data (e.g., which may be provided by law, policy, industry or organizational practice, etc.).

As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). In particular embodiments, a data subject access request fulfillment system may utilize one or more data model generation and population techniques (e.g., such as any suitable technique described herein) to create a centralized data map with which the system can identify personal data stored, collected, or processed for a particular data subject, a reason for the processing, and any other information related to the processing.

In various embodiments, the system may be adapted for: (1) automatically verifying an identity of a particular data subject access data subject placing the data subject access request (DSAR); (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically obtaining, from a particular data model, at least a portion of information requested in the first data subject access request; and (3) after obtaining the at least a portion of the requested information, displaying the obtained information to a user as part of a fulfillment of the first data subject access request. The information requested in the first data subject access request may, for example, comprise at least substantially all (e.g., most or all) of the information regarding the first data subject that is stored within the data model.

In various embodiments, the system is adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the first data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically facilitating an update of personal data that an organization associated with the first webform is processing regarding the particular data subject access requestor.

Similarly, in particular embodiments, the system may be adapted for: (1) automatically verifying, by at least one computer processor, an identity of a particular data subject access requestor placing the data subject access request; and (2) at least partially in response to verifying the identity of the particular data subject access requestor, automatically processing a request, made by the particular data subject access requestor, to opt out of having the organization use the particular data subject access requestor's personal information in one or more particular ways.

In various embodiments, the system is configured to automatically identify a data subject using a random identifier stored in a cookie. The system may, for example, automatically capture one or more consent records related to the individual data subject based on the cookie data. The system may, for example, use a unique cookie generated in response to a user visiting a website through which the user provided consent for an initial processing of information. The system may then use the cookie data to confirm the identity of the user when the user later submits a DSAR (e.g., to modify consent, request collected data, etc.).

Data Subject Cookie Verification Module and Related Methods

As discussed in more detail herein, a data subject may submit a subject access request, for example, to request a listing of any personal information that a particular organization is currently storing regarding the data subject, to request that the personal data be deleted, to opt out of allowing the organization to process the personal data, etc. In various embodiments, the system is configured to verify an identity of a data subject by using a random identifier stored in a cookie. The system may, for example, automatically capture one or more consent records related to the individual data subject based on the cookie data. The system may, for example, use a unique cookie generated in response to a user visiting a website through which the user provided consent for an initial processing of information. The system may then use the cookie data to confirm the identity of the user when the user later submits a DSAR (e.g., to modify consent, request collected data, etc.).

In particular embodiments, a Data Subject Cookie Verification Module 7100 is configured to receive a request to initiate a transaction between an entity and a data subject, generate (i) a consent receipt for the transaction comprising at least a unique subject identifier and a unique consent receipt key and (ii) a unique cookie to identify the data subject's transaction initiated by the data subject, store the consent receipt for the transaction and the unique cookie, receive a data subject access request from the data subject, verify an identity of the data subject based at least in part on the unique cookie, process the request by identifying one or more pieces of personal data associated with the data subject, and taking one or more actions based at least in part on the data subject access request. In particular embodiments, when processing a data subject access request, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step).

Turning to FIG. 71, when executing the Data Subject Cookie Verification Module 7100, the system begins, at Step 7110, by receiving a request to initiate a transaction between an entity and a data subject, the transaction being initiated by the data subject via a user interface and involving collection or processing of personal data associated with the data subject by the entity as part of a processing activity undertaken by the entity that the data subject is consenting to as part of the transaction. In particular embodiments, a third-party consent receipt management system may be configured to manage one or more consent receipts for a particular entity. As may be understood in light of this disclosure, a data subject may access an interaction interface (e.g., via the web) for interacting with a particular entity (e.g., one or more entity systems). The interaction interface (e.g., user interface) may include, for example, a suitable website, web form, user interface etc. The interaction interface may be provided by the entity. Using the interaction interface, a data subject may initiate a transaction with the entity that requires the data subject to provide valid consent (e.g., because the transaction includes the processing of personal data by the entity). The transaction may include, for example: (1) accessing the entity's website; (2) signing up for a user account with the entity; (3) signing up for a mailing list with the entity; (4) a free trial sign up; (5) product registration; and/or (6) any other suitable transaction that may result in collection and/or processing personal data, by the entity, about the data subject.

As may be understood from this disclosure, any particular transaction may record and/or require one or more valid consents from the data subject. For example, the system may require a particular data subject to provide consent for each particular type of personal data that will be collected as part of the transaction. The system may, in various embodiments, be configured to prompt the data subject to provide valid consent, for example, by: (1) displaying, via the interaction interface, one or more pieces of information regarding the consent (e.g., what personal data will be collected, how it will be used, etc.); and (2) prompt the data subject to provide the consent.

In response to the data subject (e.g., or the entity) initiating the transaction, the system may be configured to: (1) generate a unique receipt key (e.g., unique receipt ID); (2) associate the unique receipt key with the data subject (e.g., a unique subject identifier), the entity, and the transaction; and (3) electronically store (e.g., in computer memory) the unique receipt key. The system may further store a unique user ID (e.g., unique subject identifier) associated with the data subject (e.g., a hashed user ID, a unique user ID provided by the data subject, unique ID based on a piece of personal data such as an e-mail address, etc.).

Continuing to Step 7120, the system is configured for generating: (i) a consent receipt for the transaction comprising at least a unique subject identifier and a unique consent receipt key and (ii) a unique cookie to identify the data subject's transaction initiated by the via the user interface. In various embodiments, a third-party data repository system is configured to facilitate the receipt and centralized storage of personal data for each of a plurality of respective data subjects. In particular embodiments, the system may be configured to: (1) receive personal data associated with a particular data subject (e.g., a copy of the data, a link to a location of where the data is stored, etc.); and (2) store the personal data in a suitable data format (e.g., a data model, a reference table, etc.) for later retrieval. In other embodiments, the system may be configured to receive an indication that personal data has been collected regarding a particular data subject (e.g., collected by a first party system, a software application utilized by a particular entity, etc.).

In particular embodiments, the third party data repository system is configured to: (1) receive an indication that a first party system (e.g., entity) has collected and/or processed a piece of personal data for a data subject; (2) determine a location in which the first party system has stored the piece of personal data; (3) optionally digitally store (e.g., in computer memory) a copy of the piece of personal data and associate, in memory, the piece of personal data with the data subject; and (4) optionally digitally store an indication of the storage location utilized by the first party system for the piece of personal data. In particular embodiments, the system is configured to provide a centralized database, for each particular data subject (e.g., each particular data subject about whom a first party system collects or has collected personally identifiable information), of any personal data processed and/or collected by a particular entity.

In particular embodiments, a third-party data repository system is configured to interface with a consent receipt management system (e.g., such as the consent receipt management system described herein). In particular embodiments, the system may, for example: (1) receive an indication of a consent receipt having an associated unique subject identifier and one or more receipt definitions (e.g., such as any suitable definition described herein); (2) identify, based at least in part on the one or more receipt definitions, one or more pieces of repository data associated with the consent receipt (e.g., one or more data elements or pieces of personal data for which the consent receipt provides consent to process; a storage location of the one or more data elements for which the consent receipt provides consent to process; etc.); (3) digitally store the unique subject identifier in one or more suitable data stores; and (4) digitally associate the unique subject identifier with the one or more pieces of repository data. In particular embodiments, the system is configured to store the personal data provided as part of the consent receipt in association with the unique subject identifier.

As may be understood from this disclosure, any particular transaction may record and/or require one or more valid consents from the data subject. For example, the system may require a particular data subject to provide consent for each particular type of personal data that will be collected as part of the transaction. In response to the data subject (e.g., or the entity) initiating the transaction, the system may be configured to: (1) generate a unique receipt key (e.g., unique receipt ID); (2) associate the unique receipt key with the data subject (e.g., a unique subject identifier), the entity, and the transaction; and (3) electronically store (e.g., in computer memory) the unique receipt key. The system may further store a unique user ID (e.g., unique subject identifier) associated with the data subject (e.g., a hashed user ID, a unique user ID provided by the data subject, unique ID based on a piece of personal data such as an e-mail address, etc.).

In particular embodiments, the unique consent receipt key may be associated with one or more receipt definitions, which may include, for example: (1) the unique transaction ID; (2) an identity of one or more controllers and/or representatives of the entity that is engaging in the transaction with the data subject (e.g., and contact information for the one or more controllers); (3) one or more links to a privacy policy associated with the transaction at the time that consent was given; (4) a listing of one or more data types for which consent to process was provided (e.g., email, MAC address, name, phone number, browsing history, etc.); (5) one or more methods used to collect data for which consent to process was provided (e.g., using one or more cookies, receiving the personal data from the data subject directly, etc.); (6) a description of a service (e.g., a service provided as part of the transaction such as a free trial, user account, etc.); (7) one or more purposes of the processing (e.g., for marketing purposes, to facilitate contact with the data subject, etc.); (8) a jurisdiction (e.g., the European Union, United States, etc.); (9) a legal basis for the collection of personal data (e.g., consent); (10) a type of consent provided by the data subject (e.g. unambiguous, explicit, etc.); (11) one or more categories or identities of other entities to whom the personal data may be transferred; (12) one or more bases of a transfer to a third party entity (e.g., adequacy, binding corporate rules, etc.); (13) a retention period for the personal data (e.g., how long the personal data will be stored); (14) a withdrawal mechanism (e.g., a link to a withdrawal mechanism); (15) a timestamp (e.g., date and time); (16) a unique identifier for the receipt; and/or (17) any other suitable information.

In response to receiving valid consent from the data subject, the system is configured to transmit the unique transaction ID and the unique consent receipt key back to the third-party consent receipt management system for processing and/or storage. In other embodiments, the system is configured to transmit the transaction ID to a data store associated with one or more entity systems (e.g., for a particular entity on behalf of whom the third party consent receipt management system is obtaining and managing validly received consent). In further embodiments, the system is configured to transmit the unique transaction ID, the unique consent receipt key, and any other suitable information related to the validly given consent to the centralized data repository system described above for use in determining whether to store particular data and/or for assigning a unique identifier to a particular data subject for centralized data repository management purposes.

The system may be further configured to transmit a consent receipt to the data subject which may include, for example: (1) the unique transaction ID; (2) the unique consent receipt key; and/or (3) any other suitable data related to the validly provided consent. In some embodiments, the system is configured to transmit a consent receipt in any suitable format (e.g., JSON, HTML, e-mail, text, cookie, etc.). In particular embodiments, the receipt transmitted to the data subject may include a link to a subject rights portal via which the data subject may, for example: (1) view one or more provided valid consents; (2) withdraw consent; (3) etc.

The system is also configured to generate a unique cookie to identify the data subject's transaction initiated by the data subject. The system may, for example, automatically capture one or more consent records related to the individual data subject based on the cookie data. The system may, for example, use a unique cookie generated in response to a user visiting a website through which the user provided consent for an initial processing of information. The system may then use the cookie data to confirm the identity of the user when the user later submits a data subject access request (e.g., to modify consent, request collected data, etc.).

In particular embodiments, when the data subject initiates a transaction, the system may produce a cookie to identify the data subject, and the data subject's initiation of the transaction. The cookie may include, for example, (1) a time stamp associated with the data subject' initiation of the transaction; (2) an identifying characteristic associated with the data subject (e.g., an IP address); (3) a randomly generated set of characters or numbers, etc. In various embodiments, the consent receipt and/or the unique cookie may be electronically provided to the data subject. Additionally, the unique cookie provided to the data subject may be stored within a web browser associated with an electronic device of the data subject.

Continuing to Step 7130, the system is configured to store the consent receipt for the transaction and the unique cookie. The consent receipt and the unique cookie may be stored in one or more data assets of the entity, or in a third-party storage location. Additionally, the consent receipt and unique cookie may be stored in a common storage location or in different storage locations. At Step 7140, the system is configured for receiving a data subject access request. In various embodiments, the system receives the request via a suitable web form. In certain embodiments, the request comprises a particular request to perform one or more actions with any personal data stored by a particular organization regarding the requestor. For example, in some embodiments, the request may include a request to view one or more pieces of personal data stored by the system regarding the requestor (e.g., a subject's rights request). In other embodiments, the request may include a request to delete one or more pieces of personal data stored by the system regarding the requestor. In still other embodiments, the request may include a request to update one or more pieces of personal data stored by the system regarding the requestor (e.g., the data subject).

Continuing to Step 7150, the system is configured for verifying an identity of the data subject based at least in part on the unique cookie. In various embodiments, the system may compare the unique cookie stored by the system with one more cookie associated with the data subject that is obtained by the data subject (e.g., provided by the data subject (or electronic device of the data subject or accessed by the system)). In particular embodiments, the system may (1) access one or more cookies stored within the web browser associated with the electronic device of the data subject; (2) compare (i) the one or more cookies stored within the web browser associated with the electronic device of the data subject to (ii) the unique cookie. The system may determine that the one or more cookies stored within the web browser associated with the electronic device of the data subject includes the unique cookie, and in response, verify the identity of the data subject. Based on the comparison, the system may determine that the one or more cookies stored within the web browser associated with the electronic device of the data subject does not include the unique cookie. In response, the system may generate a notification to provide to the data subject indicating that the identity of the data subject cannot be verified, which may be electronically transmitted to the data subject. In various embodiments, when the data subject cannot be verified, the system may terminate the data subject access request, and/or one or more other verification or validation methods may be required to initiate the processing of the data subject access request.

At Step 7160, in response to verifying the identity of the data subject, the system is configured to process the request by identifying, and retrieving one or more pieces of personal data associated with the requestor that are being processed by the system. For example, in various embodiments, the system is configured to identify any personal data stored in any database, server, or other data repository associated with a particular organization. In various embodiments, the system is configured to use one or more data models, such as those described above, to identify this personal data and suitable related information (e.g., where the personal data is stored, who has access to the personal data, etc.). In various embodiments, the system is configured to use intelligent identity scanning (e.g., as described above) to identify the requestor's personal data and related information that is to be used to fulfill the request.

In still other embodiments, the system is configured to use one or more machine learning techniques to identify such personal data. For example, the system may identify particular stored personal data based on, for example, a country in which a website that the data subject request was submitted is based, or any other suitable information.

Turning to Step 7170, the system is configured to take one or more actions based at least in part on the request. In some embodiments, the system is configured to take one or more actions for which the request was submitted (e.g., display the personal data, delete the personal data, correct the personal data, etc.). In particular embodiments, the system is configured to take the one or more actions substantially automatically.

ALTERNATIVE EMBODIMENTS

In various embodiments, the system may include a recommendation engine to suggest a response and/or resolution to a privacy-related request based on various factors (country, data subject, subject type, request type, language, etc.). For example, in response to determining that a user is submitting a DSAR request from a certain country, (e.g., based on a lookup of the IP of the user), the system may determine the location of the country, native language of the country, data inventory mapping of business systems based on the type of data subject automatically, etc. The system may further determine (e.g., automatically) a priority for processing the request (based on various regulatory, timeframes for completion and business initiatives determined from metadata related to the request).

In some embodiments, the system may be configured to identify an applicable law or regulation related to the request (e.g., based on an origin location of the request, a citizenship of the requestor, etc.). In some embodiments, the system may assign a workflow for processing the request based on one or more parameters relating to the source of the request. The system may, for example, prioritize requests based on an enforcement level of failures (e.g., failure to properly respond to the request, failure to respond to the request within a specific timeframe, etc.) in various jurisdictions.

In some embodiments, the system may be configured to determine whether the system is required to return actual data to a data subject as part of a DSAR or whether metadata is sufficient. The system may, for example, dynamically determine based on regulations for a particular location whether the system can provide an automated response with metadata (e.g., a type of data stored for the data subject) as opposed to the actual data.

In still other embodiments, the system may be configured for redacting a deletion request (e.g., a DSAR including a request to delete) from a data subject based on the data mapping/inventory and the legal basis for processing a request. The system may, for example, be configured to leverage a data subject request from a data subject and utilize a system to detect the type of request. In response to determining that the request is a request to delete data for a user, the system may be configured to utilize a data map/inventory of processes and information about the legal bases for processing various data elements from the data subject involved in a process and based on the geo-location of the data subject along with a model of the regulatory environment. The system may further be configured to redact or remove parts of the deletion request and only delete data that is not otherwise required for other legal reasons (e.g. tax, contract obligation, etc.) while still deleting the data tied to consent (e.g., data that requires separate consent for the continued storage of).

In other embodiments, the system is configured to identify and map data to a common data subject profile to aggregate an individual's data in order to automatically generate a subject access request report in response to a request from the individual. The system may, for example: (1) identify a particular processing activity for which the data subject previously provided consent; (2) generate a common data subject profile for the processing activity, where the common data subject profile comprises metadata indicating one or more particular types of data collected by one or more systems as part of the data processing activity; and (3) use one or more data modelling techniques to identify each of the one or more particular types of data for the data subject. For, example, the system may generate a common data subject profile that indicates that the processing activity included the collection or processing of: (1) name; (2) e-mail address; and (3) internet search history. In response to generating the common data subject profile, the system may be configured to identify, for the data subject, each of the particular aspects of the common data subject profile for the particular data subject (e.g., name, e-mail address, and internet search history stored by one or more data systems for a particular entity). In response to identifying each of the pieces of data, the system may be configured to automatically generate a response to the data subject access request (i.e., producing the data for the data subject, deleting, etc.). In various embodiments, the system may be configured to identify a particular category of data from the common data subject profile for which the system is unable to automatically identify. In response, the system may be configured to flag the missing data type for manual review and/or processing. In other embodiments, the system may be configured to initiate a data discovery scan and/or other data discovery process (e.g., in order to locate the missing and/or unidentified data for the particular data subject), for example, using any suitable technique described herein.

In various embodiments, the system is configured to use Data Mapping Data Element classification along with intelligent identity scanning to determine how to treat data in a remote system to fulfill DSAR request. (i.e. upon deletion request, the system may use meta data to invoke different automated actions such as: data deletion, anonymization, or retention).

In various embodiments, the system may be adapted to automatically generate a task for one or more third party systems based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine one or more automated tasks to assign to one or more third party systems; and (3) automatically orchestrate a completion of the one or more tasks (e.g., by automatically completing the tasks, automatically assigning the tasks for completion, etc.

Examples of metadata that may be used to determine whether to auto-orchestrate a task for a third party system based on a particular DSAR include: (1) the type of request, (2) the location from which the request is being made, (3) current sensitivities to world events, (4) a status of the requestor (e.g., especially loyal customer, important client, competitor, employee, etc.), or (5) any other suitable metadata.

CONCLUSION

Although embodiments above are described in reference to various privacy compliance monitoring systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general.

While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be Concepted, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially Concepted as such, one or more features from a Concepted combination may in some cases be excised from the combination, and the Concepted combination may be directed to a sub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended Concepts. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation. 

What is claimed is:
 1. A method comprising: detecting, by computing hardware, a request to initiate a transaction associated with processing of personal data associated with a data subject, the request comprising an indication of consent by the data subject to the processing of the personal data; in response to detecting the request to initiate the transaction, generating, by the computing hardware, a unique consent receipt key for the transaction and transaction data for the transaction; detecting, by the computing hardware, a data subject access request associated with the data subject, the data subject access request comprising a data subject access request parameter; verifying, by the computing hardware, an identity of the data subject by comparing the transaction data to the unique consent receipt key to determine that the transaction data comprises a subset of consent receipt key data associated with the unique consent receipt key; and in response to verifying the identity of the data subject, causing, by the computing hardware and based on the data subject access request parameter, a processing of the data subject access request using the personal data.
 2. The method of claim 1, further comprising providing, by the computing hardware, the transaction data to the data subject for storage on an electronic device.
 3. The method of claim 2, wherein verifying the identity of the data subject comprises causing access of the transaction data at the electronic device.
 4. The method of claim 1, the method further comprising, in response to a failure to verify the identity of the data subject, terminating, by the computing hardware, the data subject access request.
 5. The method of claim 1, the method further comprising causing storage of the transaction data in a cookie.
 6. The method of claim 5, wherein: detecting the request to initiate the transaction occurs in response to initiation of the transaction via a web browser on a user device; and the method further comprises causing, by the computing hardware, storage of the cookie for access by the web browser.
 7. The method of claim 6, wherein: detecting the data subject access request comprises detecting the data subject access request from the web browser; and verifying the identify of the data subject comprises detecting that the cookie is accessible to the web browser.
 8. A system comprising: a non-transitory computer-readable medium storing instructions; and a processing device communicatively coupled to the non-transitory computer-readable medium, wherein, the processing device is configured to execute the instructions and thereby perform operations comprising: receiving an indication of consent by a data subject to processing of personal data associated with the data subject as part of a transaction involving the processing of the personal data; in response to receiving the indication of the consent, generating transaction data for the transaction; receiving a data subject access request associated with the data subject, the data subject access request comprising a data subject access request parameter; verifying an identity of the data subject based on the transaction data; and in response to verifying the identity of the data subject, processing the data subject access request based on the data subject access request parameter using the personal data.
 9. The system of claim 8, wherein: the operations further comprise, in response to receiving the indication of the consent, generating a unique consent receipt key for the transaction; and verifying the identity of the data subject based on the transaction data comprises comparing the transaction data to receipt definitions associated with the unique consent receipt key.
 10. The system of claim 8, wherein: the operations further comprise providing the transaction data for storage on a user device; receiving the data subject access request comprises receiving the data subject access request from the user device; and verifying the identity of the data subject based on the transaction data comprises accessing the transaction data on the user device.
 11. The system of claim 8, wherein the operations further comprise generating a cookie based on the transaction data and storing the cookie at a web browser via which the indication of the consent was received.
 12. The system of claim 11, wherein receiving the data subject access request comprises receiving the data subject access request via the web browser.
 13. The system of claim 12, wherein verifying the identity of the data subject based on the transaction data comprises verifying the identity of the data subject in response to determining that the cookie is stored at the web browser.
 14. The system of claim 8, wherein: the operations further comprise, in response to receiving the indication of the consent, generating a transaction receipt for the transaction, the transaction receipt comprising receipt definitions; and transmitting the transaction receipt to a consent management system for storage.
 15. The system of claim 14, wherein verifying the identity of the data subject based on the transaction data comprises accessing the transaction receipt at the consent management system.
 16. The system of claim 14, wherein verifying the identity of the data subject based on the transaction data further comprises comparing the transaction data to the transaction receipt to determine that the transaction data comprises a subset of the receipt definitions.
 17. The system of claim 8, wherein the operations further comprise in response to a failure to verify the identity of the data subject, terminating the data subject access request.
 18. A system comprising: a non-transitory computer-readable medium storing instructions; and a processing device communicatively coupled to the non-transitory computer-readable medium, wherein, the processing device is configured to execute the instructions and thereby perform operations comprising: receiving, via a web browser on a user device, an indication of consent by a data subject to processing of personal data associated with the data subject as part of a transaction involving the processing of the personal data; in response to receiving the indication of the consent, generating transaction data for the transaction; setting a unique cookie at the web browser based on the transaction data; receiving, via the web browser on the user device, a data subject access request associated with the data subject, the data subject access request comprising a data subject access request parameter; verifying an identity of the data subject based on determining that the unique cookie is accessible to the web browser; and in response to verifying the identity of the data subject, processing the data subject access request based on the data subject access request parameter using the personal data.
 19. The system of claim 18, wherein: the operations further comprise, in response to receiving the indication of the consent, generating a unique consent receipt key for the transaction; and verifying the identity of the data subject is further based on comparing the transaction data in the unique cookie to receipt definitions associated with the unique consent receipt.
 20. The system of claim 18, wherein verifying the identity of the data subject based on determining that the unique cookie is accessible to the web browser comprises: accessing a cookie store for the web browser; accessing a plurality of cookies stored in the cookie store; and determining that the plurality of cookies include the unique cookie. 